Merge pull request #222142 from MicrosoftDocs/main

12/21 AM Publish

Author: huypub

articles/aks/azure-cni-overlay.md

@@ -4,7 +4,7 @@ description: Learn how to configure Azure CNI Overlay networking in Azure Kubern
 services: container-service
 ms.topic: article
 ms.custom: references_regions
-ms.date: 11/08/2022
+ms.date: 12/12/2022
 ---
 
 # Configure Azure CNI Overlay networking in Azure Kubernetes Service (AKS)
@@ -17,6 +17,7 @@ With Azure CNI Overlay, the cluster nodes are deployed into an Azure Virtual Net
 > Azure CNI Overlay is currently available only in the following regions:
 > - North Central US
 > - West Central US
+> - East US
 
 ## Overview of overlay networking
 
@@ -89,7 +90,6 @@ The overlay solution has the following limitations today
 * You can't deploy multiple overlay clusters on the same subnet.
 * Overlay can be enabled only for new clusters. Existing (already deployed) clusters can't be configured to use overlay.
 * You can't use Application Gateway as an Ingress Controller (AGIC) for an overlay cluster.
-* v5 VM SKUs are currently not supported.
 
 ## Install the aks-preview Azure CLI extension
 

articles/app-service/configure-connect-to-azure-storage.md

@@ -268,7 +268,7 @@ To validate that the Azure Storage is mounted successfully for the app:
 
 - To avoid potential issues related to latency, place the app and the Azure Storage account in the same Azure region. Note, however, if the app and Azure Storage account are in same Azure region, and if you grant access from App Service IP addresses in the [Azure Storage firewall configuration](../storage/common/storage-network-security.md), then these IP restrictions are not honored.
 
-- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
+- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Azure App Services stores Azure storage account key. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
 
     1. Regenerate **key2**. 
     1. In the storage mount configuration, update the access the key to use the regenerated **key2**.
@@ -297,7 +297,7 @@ To validate that the Azure Storage is mounted successfully for the app:
 
 - Mounting the storage to `/home` is not recommended because it may result in performance bottlenecks for the app. 
 
-- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
+- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Azure App Services stores Azure storage account key. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
 
     1. Regenerate **key2**. 
     1. In the storage mount configuration, update the access the key to use the regenerated **key2**.

articles/automation/troubleshoot/update-agent-issues-linux.md

@@ -103,7 +103,7 @@ As they are the directories of workspaces, the number of directories equals the
 To fix the issue, run the following command: 
 
 ```
-sudo su omsagent -c 'python /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py
+sudo su omsagent -c python /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py
 ```
 
 This command forces the omsconfig agent to talk to Azure Monitor and retrieve the latest configuration. 

articles/azure-netapp-files/backup-introduction.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 10/07/2022
+ms.date: 12/21/2022
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -28,6 +28,7 @@ Azure NetApp Files backup expands the data protection capabilities of Azure NetA
 Azure NetApp Files backup is supported for the following regions:   
 
 * Australia East
+* Canada East
 * East US
 * East US 2
 * France Central

articles/azure-netapp-files/whats-new.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 12/15/2022
+ms.date: 12/21/2022
 ms.author: anfdocs
 ---
 # What's new in Azure NetApp Files
@@ -21,7 +21,26 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## December 2022
 
-  * [Cross-zone replication](create-cross-zone-replication.md) (Preview)
+* [Azure Application Consistent Snapshot tool (AzAcSnap) 7](azacsnap-introduction.md) 
+    
+    Azure Application Consistent Snapshot Tool (AzAcSnap) is a command-line tool that enables customers to simplify data protection for third-party databases in Linux environments. 
+
+    AzAcSnap 7 is being released with the following fixes and improvements: 
+    * Shortening of snapshot names
+    * Restore (`-c restore`) improvements
+    * Test (`-c test`) improvements 
+    * Validation improvements 
+    * Timeout improvements 
+    * Azure Backup integration improvements 
+    * Features moved to GA (generally available):
+        None
+    * The following features are now in preview: 
+        * Preliminary support for [Azure NetApp Files backup](backup-introduction.md)
+        * [IBM Db2 database](https://www.ibm.com/products/db2) support adding options to configure, test, and snapshot backup IBM Db2 in an application consistent manner
+
+    Download the latest release of the installer [here](https://aka.ms/azacsnapinstaller). 
+
+* [Cross-zone replication](create-cross-zone-replication.md) (Preview)
 
     With Azure’s push towards the use of availability zones (AZs) the need for storage-based data replication is equally increasing. Azure NetApp Files now supports [cross-zone replication](cross-zone-replication-introduction.md). With this new in-region replication capability - by combining it with the new availability zone volume placement feature - you can replicate your Azure NetApp Files volumes asynchronously from one Azure availability zone to another in a fast and cost-effective way.
 

articles/cosmos-db/nosql/how-to-configure-cosmos-db-trigger.md

@@ -5,7 +5,7 @@ author: ealsur
 ms.service: cosmos-db
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 07/06/2022
+ms.date: 12/21/2022
 ms.author: maquaran
 ---
 
@@ -40,7 +40,7 @@ After the Azure Function is deployed with the updated configuration, you'll see
 
 ### Which type of logs are emitted?
 
-Once enabled, there are three levels of log events that will be emitted:
+Once enabled, there are four levels of log events that will be emitted:
 
 * Error:
   * When there's an unknown or critical error on the Change Feed processing that is affecting the correct trigger functionality.
@@ -49,6 +49,9 @@ Once enabled, there are three levels of log events that will be emitted:
   * When your Function user code had an unhandled exception - There's a gap in your Function code and the Function isn't [resilient to errors](../../azure-functions/performance-reliability.md#write-defensive-functions) or a serialization error (for C# Functions, the raw json can't be deserialized to the selected C# type).
   * When there are transient connectivity issues preventing the trigger from interacting with the Azure Cosmos DB account. The trigger will retry these [transient connectivity errors](troubleshoot-dotnet-sdk-request-timeout.md) but if they extend for a long period of time, there could be a network problem. You can enable Debug level traces to obtain the Diagnostics from the underlying Azure Cosmos DB SDK.
 
+* Information:
+  * When a lease is taken to another instance - During initialization and when the Function scales, the leases can be rebalanced to another instance. If you customized the acquire or expiration intervals, it can also indicate that the values might be inappropriate (the expiration interval is lower than renewal).
+
 * Debug:
   * When a lease is acquired by an instance - The current instance will start processing the Change Feed for the lease.
   * When a lease is released by an instance - The current instance has stopped processing the Change Feed for the lease.

articles/defender-for-cloud/TOC.yml

@@ -646,7 +646,9 @@
     - name: Latest updates in the regulatory compliance dashboard
       href: episode-twenty-one.md
     - name: Defender EASM
-      href: episode-twenty-two.md 
+      href: episode-twenty-two.md
+    - name: Defender Threat Intelligence (Defender TI)
+      href: episode-twenty-three.md 
   - name: Manage user data
     href: privacy.md
   - name: Microsoft Defender for IoT documentation

articles/defender-for-cloud/episode-twenty-three.md

@@ -0,0 +1,43 @@
+---
+title: Defender Threat Intelligence  | Defender for Cloud in the field
+titleSuffix: Microsoft Defender for Cloud
+description: Learn about Microsoft Defender Threat Intelligence (Defender TI)
+ms.topic: reference
+ms.date: 12/21/2022
+---
+
+# Defender threat Intelligence | Defender for Cloud in the Field
+
+**Episode description**: In this episode of Defender for Cloud in the Field, Alexandra Roland joins Yuri Diogenes to talk about Microsoft Defender Threat Intelligence (Defender TI). Alexandra explains how Defender TI works and how it integrates with Defender EASM. Alexandra goes over an end-to-end scenario to demonstrate how to use Defender TI to perform a security investigation based on the data collected by the platform.
+<br>
+<br>
+<iframe src="https://aka.ms/docs/player?id=adfb8027-21ca-4bd0-9e54-28b0d642558a" width="1080" height="530" allowFullScreen="true" frameBorder="0"></iframe>
+
+- [04:09](/shows/mdc-in-the-field/threat-intelligence#time=04m09s) - How Defender for Cloud leverages Defender TI
+
+- [05:25](/shows/mdc-in-the-field/threat-intelligence#time=05m25s) - What is reputation score in Defender TI
+
+- [07:15](/shows/mdc-in-the-field/threat-intelligence#time=07m15s) - How to try Defender TI
+
+- [08:45](/shows/mdc-in-the-field/threat-intelligence#time=08m45s) - Demonstration
+
+
+## Recommended resources
+  - [Learn more](https://learn.microsoft.com/defender/threat-intelligence/what-is-microsoft-defender-threat-intelligence-defender-ti) about Defender TI.
+  - Subscribe to [Microsoft Security on YouTube](https://www.youtube.com/playlist?list=PL3ZTgFEc7LysiX4PfHhdJPR7S8mGO14YS)
+  - Join our [Tech Community](https://aka.ms/SecurityTechCommunity)
+  - For more about [Microsoft Security](https://msft.it/6002T9HQY)
+
+- Follow us on social media:
+
+     - [LinkedIn](https://www.youtube.com/redirect?event=video_description&redir_token=QUFFLUhqbFk5TXZuQld2NlpBRV9BQlJqMktYSm95WWhCZ3xBQ3Jtc0tsQU13MkNPWGNFZzVuem5zc05wcnp0VGxybHprVTkwS2todWw0b0VCWUl4a2ZKYVktNGM1TVFHTXpmajVLcjRKX0cwVFNJaDlzTld4MnhyenBuUGRCVmdoYzRZTjFmYXRTVlhpZGc4MHhoa3N6ZDhFMA&q=https%3A%2F%2Fwww.linkedin.com%2Fshowcase%2Fmicrosoft-security%2F)
+     - [Twitter](https://twitter.com/msftsecurity)
+
+- Join our [Tech Community](https://aka.ms/SecurityTechCommunity)
+
+- Learn more about [Microsoft Security](https://msft.it/6002T9HQY)
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [New AWS Connector in Microsoft Defender for Cloud](episode-one.md)

articles/defender-for-cloud/episode-twenty-two.md

@@ -42,4 +42,4 @@ ms.date: 12/01/2022
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [New AWS Connector in Microsoft Defender for Cloud](episode-one.md)
+> [Defender Threat Intelligence (Defender TI)](episode-twenty-three.md)

articles/defender-for-iot/device-builders/concept-event-aggregation.md

@@ -149,26 +149,26 @@ The data collected on each package includes:
 
 ## Peripheral events (event-based collector)
 
-Collects connections and disconnections of USB and Ethernet.
+The Peripheral events collector collect connections and disconnections of USB and Ethernet events.
 
 Collected fields depend on the type of event:
 
-**USB event**
+**USB events**
 
 | Parameter | Description|
 |--|--|
 | **Timestamp** | The time the event occurred. |
 | **ActionType** | Whether the event was a connection or disconnection event. |
 | **bus_number** | Specific controller identifier, each USB device can have several. |
 | **kernel_device_number** | Representation in the kernel of the device, not unique and can each time the device is connected. |
-| **device_class** | Identifier specifying the type of device.  |
+| **device_class** | Identifier specifying the class of device.  |
 | **device_subclass** | Identifier specifying the type of device. |
-| **device_protocol** | Identifier specifying the protocol of device. |
+| **device_protocol** | Identifier specifying the device protocol. |
 | **interface_class** | In case device class is 0, indicate the type of device. |
 | **interface_subclass** | In case device class is 0, indicate the type of device. |
 | **interface_protocol** | In case device class is 0, indicate the type of device. |
 
-**Ethernet event**
+**Ethernet events**
 
 | Parameter | Description|
 |--|--|
@@ -179,22 +179,22 @@ Collected fields depend on the type of event:
 
 ## File system events (event-based collector)
 
-Collects events whenever there are changes under watch directories for: creation, deletion, move and modification of directories and files.
-To define which directories and files you would like to monitor please see [System information collector specific settings](concept-micro-agent-configuration.md).
+The file system events collector collects events whenever there are changes under watch directories for: creation, deletion, move, and modification of directories and files.
+To define which directories and files you would like to monitor, see [System information collector specific settings](concept-micro-agent-configuration.md).
 
 The following data is collected:
 
 | Parameter | Description|
 |--|--|
 | **Timestamp** | The time the event occurred. |
-| **Mask** | Linux inotify mask related to the file system event, the mask identify the type of the action and can be one of the following: Access/Modified/Metadata changed/Closed/Opened/Moved/Created/Deleted. |
+| **Mask** | Linux inotify mask related to the file system event, the mask identifies the type of the action and can be one of the following: Access/Modified/Metadata changed/Closed/Opened/Moved/Created/Deleted. |
 | **Path** | Directory/file path the event was generated to. |
 | **Hitcount** | Number of times this event was aggregated. |
 
 ## Statistics data (trigger-based collector)
 
-The Statistics collector generates various statistics on the different micro agent collectors, these statistics provide information about the performance of the collectors in the previous collection cycle.
-Examples of possible statistics include the number of events that were successfully sent and the number of events that were dropped, along with the reasons for the failures.
+The Statistics collector generates various statistics on the different micro agent collectors. These statistics provide information about the performance of the collectors in the previous collection cycle.
+Examples of possible statistics include the number of events that were successfully sent, and the number of events that were dropped, along with the reasons for the failures.
 
 Collected fields: