Merge pull request #214680 from MicrosoftDocs/main

Publish to live, Sunday 4 PM PST, 10/16

Author: LJSpiller

articles/automation/automation-availability-zones.md

@@ -32,7 +32,7 @@ In the event when a zone is down, there's no action required by you to recover f
 
 ## Supported regions with availability zones
 
-See [Regions and Availability Zones in Azure](/global-infrastructure/geographies/#geographies) for the Azure regions that have availability zones. 
+See [Regions and Availability Zones in Azure](../availability-zones/az-overview.md) for the Azure regions that have availability zones. 
 Automation accounts currently support the following regions in preview: 
 
 - China North 3
@@ -70,4 +70,4 @@ There is no change to the [Service Level Agreement](https://azure.microsoft.com/
 
 ## Next steps
 
-- Learn more about [regions that support availability zones](/azure/availability-zones/az-region.md).
+- Learn more about [regions that support availability zones](../availability-zones/az-overview.md).

articles/cosmos-db/synapse-link-frequently-asked-questions.yml

@@ -21,7 +21,7 @@ sections:
       - question: |
           Is Azure Synapse Link supported for all Azure Cosmos DB APIs?
         answer: |
-          Azure Synapse Link is supported for the Azure Cosmos DB API for NoSQL and MongoDB. The support for API for Gremlin is now in preview.
+          Azure Synapse Link is supported for the Azure Cosmos DB API for NoSQL and for the Azure Cosmos DB API for MongoDB. The support for Azure Cosmos DB API for Gremlin is now in preview.
 
       - question: |
           Is Azure Synapse Link supported for multi-region Azure Cosmos DB accounts?

articles/key-vault/secrets/quick-create-bicep.md

@@ -2,14 +2,14 @@
 title: Azure Quickstart - Create an Azure key vault and a secret using Bicep | Microsoft Docs
 description: Quickstart showing how to create Azure key vaults, and add secrets to the vaults using Bicep.
 services: key-vault
-author: rkarlin
+author: msmbaldwin
 tags: azure-resource-manager
 ms.service: key-vault
 ms.subservice: secrets
 ms.topic: quickstart
 ms.custom: mvc, subject-armqs, devx-track-azurepowershell, mode-arm
 ms.date: 04/08/2022
-ms.author: rkarlin
+ms.author: mbaldwin
 #Customer intent: As a security admin who is new to Azure, I want to use Key Vault to securely store keys and passwords in Azure.
 ---
 
@@ -66,14 +66,14 @@ Two Azure resources are defined in the Bicep file:
 
     ```azurecli
     az group create --name exampleRG --location eastus
-    az deployment group create --resource-group exampleRG --template-file main.bicep --parameters keyVaultName=<vault-name> objectID=<object-id>
+    az deployment group create --resource-group exampleRG --template-file main.bicep --parameters keyVaultName=<vault-name> objectId=<object-id>
     ```
 
     # [PowerShell](#tab/PowerShell)
 
     ```azurepowershell
     New-AzResourceGroup -Name exampleRG -Location eastus
-    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -keyVaultName "<vault-name>" -objectID "<object-id>"
+    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -keyVaultName "<vault-name>" -objectId "<object-id>"
     ```
 
     ---

articles/network-watcher/media/network-watcher-nsg-flow-logging-portal/microsoft-insights-registered.png

@@ -5,7 +5,7 @@ services: network-watcher
 author: damendo
 ms.service: network-watcher
 ms.topic: tutorial
-ms.date: 11/16/2021
+ms.date: 10/17/2022
 ms.author: damendo
 ms.custom: mvc
 # Customer intent: I need to log the network traffic to and from a VM so I can analyze it for anomalies.
@@ -31,17 +31,19 @@ In this tutorial, you learn how to:
 > * Download logged data
 > * View logged data
 
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+
 ## Prerequisites
 
-- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- An Azure account with an active subscription.
 
 ## Create a virtual machine
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
 2. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines**.
 
-3. In **Virtual machines**, select **+ Create** then **+ Virtual machine**.
+3. In **Virtual machines**, select **+ Create** then **+ Azure virtual machine**.
 
 4. Enter or select the following information in **Create a virtual machine**.
 
@@ -59,7 +61,6 @@ In this tutorial, you learn how to:
     | Azure Spot instance | Leave the default. |
     | Size | Select a size. |
     | **Administrator account** |   |
-    | Authentication type | Select **SSH public key**. |
     | Username | Enter a username. |
     | Password | Enter a password. |
     | Confirm password | Confirm password. |
@@ -101,6 +102,8 @@ NSG flow logging requires the **Microsoft.Insights** provider. To register the p
 
 5. Confirm the status of the provider displayed is **Registered**. If the status is **Unregistered**, select the provider then select **Register**.
 
+    :::image type="content" source="./media/network-watcher-nsg-flow-logging-portal/microsoft-insights-registered.png" alt-text="Screenshot of registering microsoft insights provider.":::
+
 ## Enable NSG flow log
 
 NSG flow log data is written to an Azure Storage account. Complete the following steps to create a storage account for the log data.
@@ -117,12 +120,12 @@ NSG flow log data is written to an Azure Storage account. Complete the following
     | Subscription | Select your subscription. |
     | Resource group | Select **myResourceGroup**. |
     | **Instance details** |   |
-    | Storage account name | Enter a name for your storage account. </br> Must be 3-24 characters in length, can only contain lowercase letters and numbers, and must be unique across all Azure Storage. |
-    | Region | Select **(US)East US**. |
+    | Storage account name | Enter a name for your storage account. </br> Must be 3-24 characters long, and can contain only lowercase letters and numbers, and must be unique across all Azure Storage. |
+    | Region | Select **(US) East US**. |
     | Performance | Leave the default of **Standard**. |
     | Redundancy | Leave the default of **Geo-redundant storage (GRS)**. |
 
-4. Select **Review + create**.
+4. Select **Review**.
 
 5. Select **Create**.
 
@@ -182,7 +185,7 @@ The following example JSON displays data that you'll see in the PT1H.json file f
     "time": "2018-05-01T15:00:02.1713710Z",
     "systemId": "<Id>",
     "category": "NetworkSecurityGroupFlowEvent",
-    "resourceId": "/SUBSCRIPTIONS/<Id>/RESOURCEGROUPS/MYRESOURCEGROUP/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/MYVM-NSG",
+    "resourceId": "/SUBSCRIPTIONS/<subscriptionId>/RESOURCEGROUPS/MYRESOURCEGROUP/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/MYVM-NSG",
     "operationName": "NetworkSecurityGroupFlowEvents",
     "properties": {
         "Version": 1,
@@ -191,7 +194,7 @@ The following example JSON displays data that you'll see in the PT1H.json file f
                 "rule": "UserRule_default-allow-rdp",
                 "flows": [
                     {
-                        "mac": "000D3A170C69",
+                        "mac": "<macAddress>",
                         "flowTuples": [
                             "1525186745,192.168.1.4,10.0.0.4,55960,3389,T,I,A"
                         ]
@@ -206,9 +209,9 @@ The following example JSON displays data that you'll see in the PT1H.json file f
 ```json
 {
     "time": "2018-11-13T12:00:35.3899262Z",
-    "systemId": "a0fca5ce-022c-47b1-9735-89943b42f2fa",
+    "systemId": "<Id>",
     "category": "NetworkSecurityGroupFlowEvent",
-    "resourceId": "/SUBSCRIPTIONS/00000000-0000-0000-0000-000000000000/RESOURCEGROUPS/FABRIKAMRG/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/FABRIAKMVM1-NSG",
+    "resourceId": "/SUBSCRIPTIONS/<subscriptionId>/RESOURCEGROUPS/MYRESOURCEGROUP/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/MYVM-NSG",
     "operationName": "NetworkSecurityGroupFlowEvents",
     "properties": {
         "Version": 2,
@@ -217,7 +220,7 @@ The following example JSON displays data that you'll see in the PT1H.json file f
                 "rule": "DefaultRule_DenyAllInBound",
                 "flows": [
                     {
-                        "mac": "000D3AF87856",
+                        "mac": "<macAddress>",
                         "flowTuples": [
                             "1542110402,94.102.49.190,10.5.16.4,28746,443,U,I,D,B,,,,",
                             "1542110424,176.119.4.10,10.5.16.4,56509,59336,T,I,D,B,,,,",
@@ -230,7 +233,7 @@ The following example JSON displays data that you'll see in the PT1H.json file f
                 "rule": "DefaultRule_AllowInternetOutBound",
                 "flows": [
                     {
-                        "mac": "000D3AF87856",
+                        "mac": "<macAddress>",
                         "flowTuples": [
                             "1542110377,10.5.16.4,13.67.143.118,59831,443,T,O,A,B,,,,",
                             "1542110379,10.5.16.4,13.67.143.117,59932,443,T,O,A,E,1,66,1,66",

articles/network-watcher/network-watcher-nsg-flow-logging-portal.md

@@ -35,7 +35,8 @@ Azure creates a canonical name DNS record (CNAME) on the public DNS. The CNAME r
 Your applications don't need to change the connection URL. When resolving to a public DNS service, the DNS server will resolve to your private endpoints. The process doesn't affect your existing applications.
 
 > [!IMPORTANT]
-> Private networks already using the private DNS zone for a given type, can only connect to public resources if they don't have any private endpoint connections, otherwise a corresponding DNS configuration is required on the private DNS zone in order to complete the DNS resolution sequence.
+> * Private networks already using the private DNS zone for a given type, can only connect to public resources if they don't have any private endpoint connections, otherwise a corresponding DNS configuration is required on the private DNS zone in order to complete the DNS resolution sequence.
+> * Private endpoint private DNS zone configurations will only automatically generate if you use the recommended naming scheme in the table below.
 
 For Azure services, use the recommended zone names as described in the following table:
 

articles/private-link/private-endpoint-dns.md

@@ -38,7 +38,7 @@ When setting up scan, you can further scope the scan after providing the databas
 
 ### Known limitations
 
-* Microsoft Purview doesn't support over 300 columns in the Schema tab and it will show "Additional-Columns-Truncated" if there are more than 300 columns.
+* Microsoft Purview doesn't support over 800 columns in the Schema tab and it will show "Additional-Columns-Truncated" if there are more than 800 columns.
 * Column level lineage is currently not supported in the lineage tab. However, the columnMapping attribute in properties tab of Azure SQL Stored Procedure Run captures column lineage in plain text.
 * Stored procedures running remotely from data integration tools like Azure Data Factory is currently not supported
 * Data lineage extraction is currently not supported for Functions, Triggers.

articles/purview/register-scan-azure-sql-database.md

@@ -27,7 +27,7 @@ This article outlines how to register dedicated SQL pools (formerly SQL DW), and
 
 ### Known limitations
 
-* Microsoft Purview doesn't support over 300 columns in the Schema tab and it will show "Additional-Columns-Truncated".
+* Microsoft Purview doesn't support over 800 columns in the Schema tab and it will show "Additional-Columns-Truncated".
 
 ## Prerequisites