Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into bastion-ddos

Author: asudbring

.openpublishing.publish.config.json

@@ -386,6 +386,12 @@
       "branch": "main",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "azureml-examples-mavaisma-r-azureml",
+      "url": "https://github.com/azure/azureml-examples",
+      "branch": "mavaisma-r-azureml",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azureml-examples-v2samplesreorg",
       "url": "https://github.com/azure/azureml-examples",

articles/active-directory-b2c/TOC.yml

@@ -66,7 +66,7 @@
     - name: Authentication library
       href: ../active-directory/develop/msal-overview.md?bc=%2fazure%2factive-directory-b2c%2fbread%2ftoc.json&toc=%2fazure%2factive-directory-b2c%2fTOC.json
       displayName: MSAL, client library, Microsoft Authentication Library
-  - name: Azure AD B2C global identitiy framework
+  - name: Azure AD B2C global identity framework
     items:
       - name: Global identity solutions
         href: azure-ad-b2c-global-identity-solutions.md

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

@@ -10,14 +10,14 @@ ms.custom: devx-track-azurepowershell
 
 ---
 
-# Move a Log Analytics workspace to different subscription or resource group
+# Move a Log Analytics workspace to a different subscription or resource group
 
-In this article, you'll learn the steps to move Log Analytics workspace to another resource group or subscription in the same region. You can learn more about moving Azure resources through the Azure portal, PowerShell, the Azure CLI, or the REST API. at [Move resources to a new resource group or subscription](../../azure-resource-manager/management/move-resource-group-and-subscription.md). 
+In this article, you'll learn the steps to move a Log Analytics workspace to another resource group or subscription in the same region. To learn more about how to move Azure resources through the Azure portal, PowerShell, the Azure CLI, or the REST API, see [Move resources to a new resource group or subscription](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
 
 > [!IMPORTANT]
-> You can't move a workspace to a different region using this procedure. Follow [move a Log Analytics workspace to another region](./move-workspace-region.md) article to move workspace across regions.
+> You can't move a workspace to a different region by using this procedure. Follow the steps in the article [Move a Log Analytics workspace to another region](./move-workspace-region.md) to move a workspace across regions.
 
-## Verify Active Directory tenant
+## Verify the Azure Active Directory tenant
 The workspace source and destination subscriptions must exist within the same Azure Active Directory tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
 
 ```powershell
@@ -26,96 +26,99 @@ The workspace source and destination subscriptions must exist within the same Az
 ```
 
 ## Workspace move considerations
-- Managed solutions that are installed in the workspace will be moved in this operation. 
-- The move operation requires that there are no Linked Services to workspace. Solutions that rely on Linked Services must be removed prior to the move, including Automation account. These solutions must be removed before you can unlink your automation account. Data collection for the solutions will stop, their tables removed from UI, but data remains in workspace per tables retention period. When adding solutions after the move, ingestion is restored and tables become visible with data. 
-  - Update Management
-  - Change Tracking
+
+Consider these points before you move a Log Analytics workspace:
+
+- Managed solutions that are installed in the workspace will be moved in this operation.
+- The move operation requires that no services can be linked to the workspace. Solutions that rely on linked services must be removed prior to the move, including an Azure Automation account. These solutions must be removed before you can unlink your Automation account. Data collection for the solutions will stop and their tables will be removed from the UI, but data will remain in the workspace per the table retention period. When you add solutions after the move, ingestion is restored and tables become visible with data. Linked services include:
+  - Update management
+  - Change tracking
   - Start/Stop VMs during off-hours
   - Microsoft Defender for Cloud
-- Workspace keys (both primary and secondary) are re-generated with workspace move operation. If you keep a copy of your workspace keys in key vault, update them with the new keys generated after the workspace move. 
-- Connected [MMA agents](../agents/log-analytics-agent.md) remain connected and keep sending data to the workspace after the move. [AMA agents](../agents/azure-monitor-agent-overview.md) via DCR will be disconnected during the move and should be reconfigured after the move.
+- Workspace keys (both primary and secondary) are regenerated with a workspace move operation. If you keep a copy of your workspace keys in Azure Key Vault, update them with the new keys generated after the workspace is moved.
+- Connected [Log Analytics agents](../agents/log-analytics-agent.md) remain connected and keep sending data to the workspace after the move. [Azure Monitor Agent](../agents/azure-monitor-agent-overview.md) will be disconnected via data collection rules during the move and should be reconfigured after the move.
 
 >[!IMPORTANT]
 > **Microsoft Sentinel customers**
-> - Currently, after Microsoft Sentinel is deployed on a workspace, moving the workspace to another resource group or subscription isn't supported. 
-> - If you have already moved the workspace, disable all active rules under **Analytics** and re-enable them after five minutes. This should be an effective solution in most cases, though, to reiterate, it is unsupported and undertaken at your own risk.
-> - It could take Azure Resource Manager a few hours to complete and solutions may be unresponsive during the operation.
-> 
-> **Re-create alerts**
-> - All alerts must be re-created because the permissions are based on workspace Resource ID, which changes during a workspace move or resource name change. Alerts in workspaces created after 1-June 2019, or in workspaces that were [upgraded from legacy Log Analytics alert API to scheduledQueryRules API](../alerts/alerts-log-api-switch.md) can be exported in template and deployed after the move. You can [check if scheduledQueryRules API is used for alerts in your workspace](../alerts/alerts-log-api-switch.md#check-switching-status-of-workspace). Alternatively, you can configure alerts manually in target workspace
+> - Currently, after Microsoft Sentinel is deployed on a workspace, moving the workspace to another resource group or subscription isn't supported.
+> - If you've already moved the workspace, disable all active rules under **Analytics** and reenable them after five minutes. This solution should be effective in most cases, although it's unsupported and undertaken at your own risk.
+> - It could take Azure Resource Manager a few hours to complete. Solutions might be unresponsive during the operation.
+>
+> **Re-create alerts:** All alerts must be re-created because the permissions are based on the workspace resource ID, which changes during a workspace move or resource name change. Alerts in workspaces created after June 1, 2019, or in workspaces that were [upgraded from the legacy Log Analytics Alert API to the scheduledQueryRules API](../alerts/alerts-log-api-switch.md) can be exported in templates and deployed after the move. You can [check if the scheduledQueryRules API is used for alerts in your workspace](../alerts/alerts-log-api-switch.md#check-switching-status-of-workspace). Alternatively, you can configure alerts manually in the target workspace.
 >
-> **Update resource paths**
-> - After a workspace move, any Azure or external resources that point to the workspace must be reviewed and updated to point to the new resource target path.
-> 
->   *Examples:*
+> **Update resource paths:** After a workspace move, any Azure or external resources that point to the workspace must be reviewed and updated to point to the new resource target path.
+>
+>   Examples:
 >   - [Azure Monitor alert rules](../alerts/alerts-resource-move.md)
 >   - Third-party applications
 >   - Custom scripting
 >
 
-### Delete solutions in Azure portal
-Use the following procedure to remove the solutions using the Azure portal:
+### Delete solutions in the Azure portal
+Use the following procedure to remove solutions by using the Azure portal:
 
-1. Open the menu for the resource group that any solutions are installed in.
-2. Select the solutions to remove.
-3. Click **Delete Resources** and then confirm the resources to be removed by clicking **Delete**.
+1. Open the menu for the resource group where any solutions are installed.
+1. Select the solutions to remove.
+1. Select **Delete Resources** and then confirm the resources to be removed by selecting **Delete**.
 
-[![Delete solutions](media/move-workspace/delete-solutions.png)](media/move-workspace/delete-solutions.png#lightbox)
+   [![Screenshot that shows deleting solutions.](media/move-workspace/delete-solutions.png)](media/move-workspace/delete-solutions.png#lightbox)
 
-### Delete using PowerShell
+### Delete by using PowerShell
 
-To remove the solutions using PowerShell, use the [Remove-AzResource](/powershell/module/az.resources/remove-azresource) cmdlet as shown in the following example:
+To remove solutions by using PowerShell, use the [Remove-AzResource](/powershell/module/az.resources/remove-azresource) cmdlet as shown in the following example:
 
 ```powershell
 Remove-AzResource -ResourceType 'Microsoft.OperationsManagement/solutions' -ResourceName "ChangeTracking(<workspace-name>)" -ResourceGroupName <resource-group-name>
 Remove-AzResource -ResourceType 'Microsoft.OperationsManagement/solutions' -ResourceName "Updates(<workspace-name>)" -ResourceGroupName <resource-group-name>
 Remove-AzResource -ResourceType 'Microsoft.OperationsManagement/solutions' -ResourceName "Start-Stop-VM(<workspace-name>)" -ResourceGroupName <resource-group-name>
 ```
 
-### Remove alert rules for Start/Stop VMs solution
-To remove **Start/Stop VMs** solution, you also need to remove the alert rules created by the solution. Use the following procedure in the Azure portal to remove these rules.
+### Remove alert rules for the Start/Stop VMs solution
+To remove the **Start/Stop VMs** solution, you also need to remove the alert rules created by the solution. Use the following procedure in the Azure portal to remove these rules:
 
 1. Open the **Monitor** menu and then select **Alerts**.
-2. Click **Manage alert rules**.
-3. Select the following three alert rules, and then click **Delete**.
+1. Select **Manage alert rules**.
+1. Select the following three alert rules, and then select **Delete**:
 
    - AutoStop_VM_Child
    - ScheduledStartStop_Parent
    - SequencedStartStop_Parent
 
-    [![Delete rules](media/move-workspace/delete-rules.png)](media/move-workspace/delete-rules.png#lightbox)
+    [![Screenshot that shows deleting rules.](media/move-workspace/delete-rules.png)](media/move-workspace/delete-rules.png#lightbox)
 
-## Unlink Automation account
-Use the following procedure to unlink the Automation account from the workspace using the Azure portal:
+## Unlink the Automation account
+Use the following procedure to unlink the Automation account from the workspace by using the Azure portal:
 
 1. Open the **Automation accounts** menu and then select the account to remove.
-2. In the **Related Resources** section of the menu, select **Linked workspace**. 
-3. Click **Unlink workspace** to unlink the workspace from your Automation account.
+1. On the **Related Resources** section of the menu, select **Linked workspace**.
+1. Select **Unlink workspace** to unlink the workspace from your Automation account.
 
-    [![Unlink workspace](media/move-workspace/unlink-workspace.png)](media/move-workspace/unlink-workspace.png#lightbox)
+    [![Screenshot that shows unlinking a workspace.](media/move-workspace/unlink-workspace.png)](media/move-workspace/unlink-workspace.png#lightbox)
 
 ## Move your workspace
 
+Move your workspace by using the Azure portal or PowerShell.
+
 ### Azure portal
-Use the following procedure to move your workspace using the Azure portal:
+Use the following procedure to move your workspace by using the Azure portal:
 
 1. Open the **Log Analytics workspaces** menu and then select your workspace.
-2. In the **Overview** page, click **change** next to either **Resource group** or **Subscription**.
-3. A new page opens with a list of resources related to the workspace. Select the resources to move to the same destination subscription and resource group as the workspace. 
-4. Select a destination **Subscription** and **Resource group**. If you're moving the workspace to another resource group in the same subscription, you won't see the **Subscription** option.
-5. Click **OK** to move the workspace and selected resources.
+1. On the **Overview** page, select **change** next to either **Resource group** or **Subscription name**.
+1. A new page opens with a list of resources related to the workspace. Select the resources to move to the same destination subscription and resource group as the workspace.
+1. Select a destination **Subscription** and **Resource group**. If you're moving the workspace to another resource group in the same subscription, you won't see the **Subscription** option.
+1. Select **OK** to move the workspace and selected resources.
 
-    [![Screenshot shows the Overview pane in the Log Analytics workspace with options to change the resource group and subscription name.](media/move-workspace/portal.png)](media/move-workspace/portal.png#lightbox)
+    [![Screenshot that shows the Overview pane in the Log Analytics workspace with options to change the resource group and subscription name.](media/move-workspace/portal.png)](media/move-workspace/portal.png#lightbox)
 
 ### PowerShell
-To move your workspace using PowerShell, use the [Move-AzResource](/powershell/module/AzureRM.Resources/Move-AzureRmResource) as in the following example:
+To move your workspace by using PowerShell, use the [Move-AzResource](/powershell/module/AzureRM.Resources/Move-AzureRmResource) cmdlet as shown in the following example:
 
 ```powershell
 Move-AzResource -ResourceId "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MyResourceGroup01/providers/Microsoft.OperationalInsights/workspaces/MyWorkspace" -DestinationSubscriptionId "00000000-0000-0000-0000-000000000000" -DestinationResourceGroupName "MyResourceGroup02"
 ```
 
 > [!IMPORTANT]
-> After the move operation, removed solutions and Automation account link should be reconfigured to bring the workspace back to its previous state.
+> After the move operation, removed solutions and the Automation account link should be reconfigured to bring the workspace back to its previous state.
 
 ## Next steps
-- For a list of which resources support move, see [Move operation support for resources](../../azure-resource-manager/management/move-support-resources.md).
+For a list of which resources support the move operation, see [Move operation support for resources](../../azure-resource-manager/management/move-support-resources.md).

articles/azure-monitor/logs/move-workspace.md

@@ -1903,7 +1903,7 @@ Before starting your move operation, review the [checklist](./move-resource-grou
 > | sites / premieraddons | **Yes** | **Yes** | No |
 > | sites / slots | **Yes** | **Yes** | No |
 > | sourcecontrols | No | No | No |
-> | staticsites | No | No | No |
+> | staticsites | Yes | Yes | No |
 
 ## Microsoft.WindowsESU
 

articles/azure-resource-manager/management/move-support-resources.md

@@ -21,7 +21,7 @@ Access tokens let Azure Communication Services SDKs [authenticate](../concepts/a
 In this quickstart, you'll learn how to use the Azure Communication Services SDKs to create identities and manage your access tokens. For production use cases, we recommend that you generate access tokens on a [server-side service](../concepts/client-and-server-architecture.md).
 
 ::: zone pivot="platform-azcli"
-[!INCLUDE [Azure CLI](./includes/access-tokens/access-token-azcli.md)]
+[!INCLUDE [Azure CLI](./includes/access-tokens/access-token-az-cli.md)]
 ::: zone-end
 
 ::: zone pivot="programming-language-csharp"

articles/communication-services/quickstarts/access-tokens.md

@@ -18,7 +18,7 @@ ms.custom: mode-other
 Get started with Azure Communication Services by using the Communication Services Chat SDK to add real-time chat to your application. In this quickstart, we'll use the Chat SDK to create chat threads that allow users to have conversations with one another. To learn more about Chat concepts, visit the [chat conceptual documentation](../../concepts/chat/concepts.md).
 
 ::: zone pivot="platform-azcli"
-[!INCLUDE [Chat with Azure CLI](./includes/chat-azcli.md)]
+[!INCLUDE [Chat with Azure CLI](./includes/chat-az-cli.md)]
 ::: zone-end
 
 ::: zone pivot="programming-language-javascript"

articles/communication-services/quickstarts/chat/get-started.md

@@ -31,7 +31,7 @@ Get started with Azure Communication Services by provisioning your first Communi
 ::: zone-end
 
 ::: zone pivot="platform-azcli"
-[!INCLUDE [Azure CLI](./includes/create-resource-azcli.md)]
+[!INCLUDE [Azure CLI](./includes/create-resource-az-cli.md)]
 ::: zone-end
 
 ::: zone pivot="platform-net"

articles/communication-services/quickstarts/chat/includes/chat-azcli.md renamed to articles/communication-services/quickstarts/chat/includes/chat-az-cli.md

@@ -21,7 +21,7 @@ Teams external users are authenticated as Azure Communication Services users in
 In this quickstart, you'll learn how to use the Azure Communication Services SDKs to create identities and manage your access tokens. For production use cases, we recommend that you generate access tokens on a [server-side service](../../concepts/client-and-server-architecture.md).
 
 ::: zone pivot="platform-azcli"
-[!INCLUDE [Azure CLI](../includes/access-tokens/access-token-azcli.md)]
+[!INCLUDE [Azure CLI](../includes/access-tokens/access-token-az-cli.md)]
 ::: zone-end
 
 ::: zone pivot="programming-language-csharp"