Merge pull request #215563 from MicrosoftDocs/main

Publish main to live, Sunday 10/23 4 PM

Author: jborsecnik

articles/azure-monitor/logs/customer-managed-keys.md

@@ -279,6 +279,8 @@ N/A
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
+az account set —subscription "storage-account-subscription-id"
+
 $storageAccountId = '/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Storage/storageAccounts/<storage name>'
 
 az account set —subscription "workspace-subscription-id"
@@ -289,11 +291,13 @@ az monitor log-analytics workspace linked-storage create —type Query —resour
 # [PowerShell](#tab/powershell)
 
 ```powershell
-$storageAccount.Id = Get-AzStorageAccount -ResourceGroupName "resource-group-name" -Name "storage-account-name"
+Select-AzSubscription "StorageAccount-subscription-id"
+
+$storageAccountId = (Get-AzStorageAccount -ResourceGroupName "resource-group-name" -Name "storage-account-name").id
 
 Select-AzSubscription "workspace-subscription-id"
 
-New-AzOperationalInsightsLinkedStorageAccount -ResourceGroupName "resource-group-name" -WorkspaceName "workspace-name" -DataSourceType Query -StorageAccountIds $storageAccount.Id
+New-AzOperationalInsightsLinkedStorageAccount -ResourceGroupName "resource-group-name" -WorkspaceName "workspace-name" -DataSourceType Query -StorageAccountIds $storageAccountId
 ```
 
 # [REST](#tab/rest)
@@ -329,6 +333,8 @@ N/A
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
+az account set —subscription "storage-account-subscription-id"
+
 $storageAccountId = '/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Storage/storageAccounts/<storage name>'
 
 az account set —subscription "workspace-subscription-id"
@@ -339,11 +345,13 @@ az monitor log-analytics workspace linked-storage create —type ALerts —resou
 # [PowerShell](#tab/powershell)
 
 ```powershell
-$storageAccount.Id = Get-AzStorageAccount -ResourceGroupName "resource-group-name" -Name "storage-account-name"
+Select-AzSubscription "StorageAccount-subscription-id"
+
+$storageAccountId = (Get-AzStorageAccount -ResourceGroupName "resource-group-name" -Name "storage-account-name").id
 
 Select-AzSubscription "workspace-subscription-id"
 
-New-AzOperationalInsightsLinkedStorageAccount -ResourceGroupName "resource-group-name" -WorkspaceName "workspace-name" -DataSourceType Alerts -StorageAccountIds $storageAccount.Id
+New-AzOperationalInsightsLinkedStorageAccount -ResourceGroupName "resource-group-name" -WorkspaceName "workspace-name" -DataSourceType Alerts -StorageAccountIds $storageAccountId
 ```
 
 # [REST](#tab/rest)

articles/azure-monitor/logs/logs-data-export.md

@@ -39,7 +39,7 @@ Log Analytics workspace data export continuously exports data that is sent to yo
 - You can define up to 10 enabled rules in your workspace. More rules are allowed when disabled. 
 - Destinations must be in the same region as the Log Analytics workspace.
 - Storage Account must be unique across rules in workspace.
-- Tables names can be no longer than 60 characters when exporting to Storage Account and 47 characters to Event Hubs. Tables with longer names will not be exported.
+- Tables names can be 60 characters long when exporting to Storage Account, and 47 characters to Event Hubs. Tables with longer names won't be exported.
 - Data export isn't supported in China currently.
 
 ## Data completeness
@@ -151,8 +151,7 @@ If you have configured your Storage Account to allow access from selected networ
 Data export rule defines the destination and tables for which data is exported. You can create 10 rules in 'enable' state in your workspace, more rules are allowed in 'disable' state. Storage Account must be unique across rules in workspace. Multiple rules can use the same Event Hubs namespace when sending to separate Event Hubs.
 
 > [!NOTE]
-> - You can include tables that aren't yet supported in export, and no data will be exported for these until the tables are supported.
-> - The legacy custom log won’t be supported in export. The next generation of custom log available in preview early 2022 can be exported.
+> - You can include tables that aren't yet supported in rules, but no data will be exported for these until tables get supported.
 > - Export to Storage Account - a separate container is created in Storage Account for each table.
 > - Export to Event Hubs - if Event Hubs name isn't provided, a separate Event Hubs is created for each table. The [number of supported Event Hubs in 'Basic' and 'Standard' namespaces tiers is 10](../../event-hubs/event-hubs-quotas.md#common-limits-for-all-tiers). When exporting more than 10 tables to these tiers, either split the tables between several export rules to different Event Hubs namespaces, or provide an Event Hubs name in the rule to export all tables to it.
 

articles/cognitive-services/Speech-Service/how-to-speech-synthesis-viseme.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: how-to
-ms.date: 09/16/2022
+ms.date: 10/23/2022
 ms.author: yulili
 ms.devlang: cpp, csharp, java, javascript, python
 ms.custom: references_regions
@@ -62,9 +62,9 @@ Visemes vary by language and locale. Each locale has a set of visemes that corre
 |6|`j`, `i`, `ɪ` |<img src="media/text-to-speech/viseme-id-6.jpg" width="200" height="200" alt="The mouth position when viseme ID is 6">|
 |7|`w`, `u`|<img src="media/text-to-speech/viseme-id-7.jpg" width="200" height="200" alt="The mouth position when viseme ID is 7">|
 |8|`o`|<img src="media/text-to-speech/viseme-id-8.jpg" width="200" height="200" alt="The mouth position when viseme ID is 8">|
-|9|Not supported|<img src="media/text-to-speech/viseme-id-9.jpg" width="200" height="200" alt="The mouth position when viseme ID is 9">|
-|10|Not supported|<img src="media/text-to-speech/viseme-id-10.jpg" width="200" height="200" alt="The mouth position when viseme ID is 10">|
-|11|Not supported|<img src="media/text-to-speech/viseme-id-11.jpg" width="200" height="200" alt="The mouth position when viseme ID is 11">|
+|9|`aʊ`|<img src="media/text-to-speech/viseme-id-9.jpg" width="200" height="200" alt="The mouth position when viseme ID is 9">|
+|10|`ɔɪ`|<img src="media/text-to-speech/viseme-id-10.jpg" width="200" height="200" alt="The mouth position when viseme ID is 10">|
+|11|`aɪ`|<img src="media/text-to-speech/viseme-id-11.jpg" width="200" height="200" alt="The mouth position when viseme ID is 11">|
 |12|`h`|<img src="media/text-to-speech/viseme-id-12.jpg" width="200" height="200" alt="The mouth position when viseme ID is 12">|
 |13|`ɹ`|<img src="media/text-to-speech/viseme-id-13.jpg" width="200" height="200" alt="The mouth position when viseme ID is 13">|
 |14|`l`|<img src="media/text-to-speech/viseme-id-14.jpg" width="200" height="200" alt="The mouth position when viseme ID is 14">|
@@ -243,7 +243,7 @@ Here's an example of the viseme output.
 
 # [2D SVG](#tab/2dsvg)
 
-The SVG output is a xml string that contains the animation.
+The SVG output is an xml string that contains the animation.
 Render the SVG animation along with the synthesized speech to see the mouth movement.
 
 ```xml

articles/cognitive-services/Speech-Service/includes/phonetic-sets/text-to-speech/en-us.md

@@ -20,9 +20,9 @@
 | ow     | `oʊ`  | 8,4      | **o**ld       | cl**o**ne | g**o**                      |
 | uw     | `u`   | 7        | **U**ber      | b**oo**st | t**oo**                     |
 | ah     | `ʌ`   | 1        | **u**ncle     | c**u**t   |                             |
-| ay     | `aɪ`  | 2,6      | **i**ce       | b**i**te  | fl**y**                     |
-| aw     | `aʊ`  | 2,4      | **ou**t       | s**ou**th | c**ow**                     |
-| oy     | `ɔɪ`  | 3,6      | **oi**l       | j**oi**n  | t**oy**                     |
+| ay     | `aɪ`  | 11       | **i**ce       | b**i**te  | fl**y**                     |
+| aw     | `aʊ`  | 9        | **ou**t       | s**ou**th | c**ow**                     |
+| oy     | `ɔɪ`  | 10       | **oi**l       | j**oi**n  | t**oy**                     |
 | y uw   | `ju`  | 6,7      | **Yu**ma      | h**u**man | f**ew**                     |
 | ax     | `ə`   | 1        | **a**go       | wom**a**n | are**a**                    |
 
@@ -33,8 +33,8 @@
 | ih r   | `ɪɹ`  | 6,13     | **ear**s     | t**ir**amisu   | n**ear**   |
 | eh r   | `ɛɹ`  | 4,13     | **air**plane | app**ar**ently | sc**ar**e  |
 | uh r   | `ʊɹ`  | 4,13     |              |                | c**ur**e   |
-| ay r   | `aɪɹ` | 2,6,13   | **Ire**land  | f**ir**eplace  | ch**oir**  |
-| aw r   | `aʊɹ` | 2,4,13   | **hour**s    | p**ower**ful   | s**our**   |
+| ay r   | `aɪɹ` | 11,13    | **Ire**land  | f**ir**eplace  | ch**oir**  |
+| aw r   | `aʊɹ` | 9,13     | **hour**s    | p**ower**ful   | s**our**   |
 | ao r   | `ɔɹ`  | 3,13     | **or**ange   | m**or**al      | s**oar**   |
 | aa r   | `ɑɹ`  | 2,13     | **ar**tist   | st**ar**t      | c**ar**    |
 | er r   | `ɝ`   | 5        | **ear**th    | b**ir**d       | f**ur**    |

articles/data-factory/connector-azure-blob-storage.md

@@ -8,7 +8,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 09/01/2022
+ms.date: 10/23/2022
 ---
 
 # Copy and transform data in Azure Blob Storage by using Azure Data Factory or Azure Synapse Analytics
@@ -684,7 +684,7 @@ In this case, all files that were sourced under `/data/sales` are moved to `/bac
 
 **Filter by last modified:** You can filter which files you process by specifying a date range of when they were last modified. All datetimes are in UTC. 
 
-**Enable change data capture:** If true, you will get new or changed files only from the last run. Initial load of full snapshot data will always be gotten in the first run, followed by capturing new or changed files only in next runs. For more details, see [Change data capture](#change-data-capture-preview).
+**Enable change data capture:** If true, you will get new or changed files only from the last run. Initial load of full snapshot data will always be gotten in the first run, followed by capturing new or changed files only in next runs. 
 
 :::image type="content" source="media/data-flow/enable-change-data-capture.png" alt-text="Screenshot showing Enable change data capture.":::
 
@@ -847,15 +847,11 @@ To learn details about the properties, check [Delete activity](delete-activity.m
 ]
 ```
 
-## Change data capture (preview) 
+## Change data capture 
 
-Azure Data Factory can get new or changed files only from Azure Blob Storage by enabling **Enable change data capture (Preview)** in the mapping data flow source transformation. With this connector option, you can read new or updated files only and apply transformations before loading transformed data into destination datasets of your choice.
+Azure Data Factory can get new or changed files only from Azure Blob Storage by enabling **Enable change data capture ** in the mapping data flow source transformation. With this connector option, you can read new or updated files only and apply transformations before loading transformed data into destination datasets of your choice. Pleaser refer to [Change Data Capture](https://learn.microsoft.com/azure/data-factory/concepts-change-data-capture) for detials.
 
-Make sure you keep the pipeline and activity name unchanged, so that the checkpoint can always be recorded from the last run to get changes from there. If you change your pipeline name or activity name, the checkpoint will be reset, and you will start from the beginning in the next run.
-
-When you debug the pipeline, the **Enable change data capture (Preview)** works as well. Be aware that the checkpoint will be reset when you refresh your browser during the debug run. After you are satisfied with the result from debug run, you can publish and trigger the pipeline. It will always start from the beginning regardless of the previous checkpoint recorded by debug run. 
-
-In the monitoring section, you always have the chance to rerun a pipeline. When you are doing so, the changes are always gotten from the checkpoint record in your selected pipeline run. 
+. 
 
 ## Next steps
 

articles/data-factory/control-flow-append-variable-activity.md

@@ -9,7 +9,7 @@ ms.topic: conceptual
 author: chez-charlie
 ms.author: chez
 ms.reviewer: jburchel
-ms.date: 09/09/2021
+ms.date: 10/23/2022
 ---
 
 # Append Variable activity in Azure Data Factory and Synapse Analytics

articles/defender-for-cloud/media/protect-network-resources/workload-protection-network-map.png

@@ -2,7 +2,7 @@
 title: Protecting your network resources in Microsoft Defender for Cloud
 description: This document addresses recommendations in Microsoft Defender for Cloud that help you protect your Azure network resources and stay in compliance with security policies.
 ms.topic: conceptual
-ms.date: 11/09/2021
+ms.date: 10/23/2022
 ---
 # Protect your network resources
 
@@ -35,7 +35,7 @@ To open the Network map:
 
 1. Select **Network map**.
 
-    :::image type="content" source="./media/protect-network-resources/opening-network-map.png" alt-text="Opening the network map from the Workload protections." lightbox="./media/protect-network-resources/opening-network-map.png":::
+:::image type="content" source="media/protect-network-resources/workload-protection-network-map.png" alt-text="Screenshot showing selection of network map from workload protections." lightbox="media/protect-network-resources/workload-protection-network-map.png":::
 
 1. Select the **Layers** menu choose **Topology**.
 

articles/defender-for-cloud/protect-network-resources.md

@@ -100,12 +100,6 @@ To locate the unique numeric ID in the GCP portal, navigate to **IAM & Admin** >
 
 1. (Optional) If you changed any of the names of any of the resources, update the names in the appropriate fields.
 
-1. (**Servers/SQL only**) Select **Azure-Arc for servers onboarding**
-
-    :::image type="content" source="media/quickstart-onboard-gcp/unique-numeric-id.png" alt-text="Screenshot showing the Azure-Arc for servers onboarding section of the screen." lightbox="media/quickstart-onboard-gcp/unique-numeric-id.png":::
-
-    Enter the service account unique ID, which is generated automatically after running the GCP Cloud Shell. 
-
 1. Select the **Next: Review and generate >**.
 
 1. Ensure the information presented is correct.

articles/defender-for-cloud/quickstart-onboard-gcp.md

@@ -2,7 +2,7 @@
 title: Important changes coming to Microsoft Defender for Cloud
 description: Upcoming changes to Microsoft Defender for Cloud that you might need to be aware of and for which you might need to plan 
 ms.topic: overview
-ms.date: 10/20/2022
+ms.date: 10/23/2022
 ---
 
 # Important upcoming changes to Microsoft Defender for Cloud
@@ -18,7 +18,13 @@ If you're looking for the latest release notes, you'll find them in the [What's
 
 | Planned change | Estimated date for change |
 |--|--|
-| None | None |
+| [Deprecation of AWS Lambda recommendation](#deprecation-of-aws-lambda-recommendation) | November 2023 |
+
+### Deprecation of AWS Lambda recommendation
+
+**Estimated date for change: November 2023**
+
+The following recommendation is set to be deprecated [`Lambda functions should have a dead-letter queue configured`](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/AwsRecommendationDetailsBlade/assessmentKey/dcf10b98-798f-4734-9afd-800916bf1e65/showSecurityCenterCommandBar~/false).
 
 ## Next steps