Merge pull request #204942 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md

@@ -230,9 +230,6 @@ You can enforce Conditional Access policies, such as multifactor authentication
 >
 > Remote desktop using Windows Hello for Business authentication is available only for deployments that use a certificate trust model. It's currently not available for a key trust model.
 
-> [!WARNING]
-> The per-user **Enabled/Enforced Azure AD Multi-Factor Authentication** setting is not supported for the Azure Windows VM Sign-In app.
-
 ## Log in by using Azure AD credentials to a Windows VM
 
 > [!IMPORTANT]
@@ -396,31 +393,12 @@ You might see the following error message when you initiate a remote desktop con
 
 ![Screenshot of the message that says the sign-in method you're trying to use isn't allowed.](./media/howto-vm-sign-in-azure-ad-windows/mfa-sign-in-method-required.png)
 
-If you've configured a Conditional Access policy that requires MFA before you can access the resource, you need to ensure that the Windows 10 or later PC that's initiating the remote desktop connection to your VM signs in by using a strong authentication method such as Windows Hello. If you don't use a strong authentication method for your remote desktop connection, you'll see the error.
+If you've configured a Conditional Access policy that requires MFA or legacy per-user Enabled/Enforced Azure AD MFA before you can access the resource, you need to ensure that the Windows 10 or later PC that's initiating the remote desktop connection to your VM signs in by using a strong authentication method such as Windows Hello. If you don't use a strong authentication method for your remote desktop connection, you'll see the error.
 
 Another MFA-related error message is the one described previously: "Your credentials did not work."
 
 ![Screenshot of the message that says your credentials didn't work.](./media/howto-vm-sign-in-azure-ad-windows/your-credentials-did-not-work.png)
 
-> [!WARNING]
-> The legacy per-user **Enabled/Enforced Azure AD Multi-Factor Authentication** setting is not supported for the Azure Windows VM Sign-In app. This setting causes sign-in to fail with the "Your credentials did not work" error message.
-
-You can resolve the problem by removing the per-user MFA setting through these commands:
-
-```
-
-# Get StrongAuthenticationRequirements configure on a user
-(Get-MsolUser -UserPrincipalName [email protected]).StrongAuthenticationRequirements
- 
-# Clear StrongAuthenticationRequirements from a user
-$mfa = @()
-Set-MsolUser -UserPrincipalName [email protected] -StrongAuthenticationRequirements $mfa
- 
-# Verify StrongAuthenticationRequirements are cleared from the user
-(Get-MsolUser -UserPrincipalName [email protected]).StrongAuthenticationRequirements
-
-```
-
 If you haven't deployed Windows Hello for Business and if that isn't an option for now, you can configure a Conditional Access policy that excludes the Azure Windows VM Sign-In app from the list of cloud apps that require MFA. To learn more about Windows Hello for Business, see [Windows Hello for Business overview](/windows/security/identity-protection/hello-for-business/hello-identity-verification).
 
 > [!NOTE]

articles/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md

@@ -15,7 +15,7 @@ In this tutorial, you'll set up a CI/CD solution using GitOps with Flux v2 and A
 
 > [!div class="checklist"]
 > * Create an Azure Arc-enabled Kubernetes or AKS cluster.
-> * Connect your application and GitOps repositories to Azure Repos or Git Hub.
+> * Connect your application and GitOps repositories to Azure Repos or GitHub.
 > * Implement CI/CD flow with either Azure Pipelines or GitHub.
 > * Connect your Azure Container Registry to Azure DevOps and Kubernetes.
 > * Create environment variable groups or secrets.

articles/defender-for-cloud/includes/defender-for-containers-enable-plan-aks.md

@@ -161,12 +161,12 @@ Request body parameters:
 
     | Property | Description |
     |----------|-------------|
-    | logAnalyticsWorkspaceResourceID | **Optional**. Full resource ID of your own Log Analytics workspace.<br>When not provided, the default workspace of the region will be used.<br><br>To get the full resource ID, run the following command to display the list of workspaces in your subscriptions in the default JSON format:<br>```az resource list --resource-type Microsoft.OperationalInsights/workspaces -o json```<br><br>The Log Analytics workspace resource ID has the following syntax:<br>/subscriptions/{your-subscription-id}/resourceGroups/{your-resource-group}/providers/Microsoft.OperationalInsights/workspaces/{your-workspace-name}. <br>Learn more in [Log Analytics workspaces](../../azure-monitor/logs/log-analytics-workspace-overview.md) |
+    | logAnalyticsWorkspaceResourceId | **Optional**. Full resource ID of your own Log Analytics workspace.<br>When not provided, the default workspace of the region will be used.<br><br>To get the full resource ID, run the following command to display the list of workspaces in your subscriptions in the default JSON format:<br>```az resource list --resource-type Microsoft.OperationalInsights/workspaces -o json```<br><br>The Log Analytics workspace resource ID has the following syntax:<br>/subscriptions/{your-subscription-id}/resourceGroups/{your-resource-group}/providers/Microsoft.OperationalInsights/workspaces/{your-workspace-name}. <br>Learn more in [Log Analytics workspaces](../../azure-monitor/logs/log-analytics-workspace-overview.md) |
 
     You can include these settings in a JSON file and specify the JSON file in the `az aks create` and `az aks update` commands with this parameter: `--defender-config <path-to-JSON-file>`. The format of the JSON file must be:
 
     ```json
-    {"logAnalyticsWorkspaceResourceID": "<workspace-id>"}
+    {"logAnalyticsWorkspaceResourceId": "<workspace-id>"}
     ```
 
     Learn more about AKS CLI commands in [az aks](/cli/azure/aks).

articles/iot-central/core/howto-faq.yml

@@ -39,7 +39,7 @@ sections:
       - question: |
           How many IoT Central applications can I deploy in my subscription?
         answer: |
-          Each Azure subscription has default quotas that could impact the scope of your IoT solution. Currently, IoT Central limits the number of applications you can deploy in a subscription to 10. If you need to increase this limit, contact [Microsoft support](https://azure.microsoft.com/support/options/).
+          Each Azure subscription has default quotas that could impact the scope of your IoT solution. Currently, IoT Central limits the number of applications you can deploy in a subscription to 100. If you need to increase this limit, contact [Microsoft support](https://azure.microsoft.com/support/options/).
                     
       - question: |
           How do I file a ticket with customer support?

articles/iot-central/core/howto-integrate-with-devops.md

@@ -52,7 +52,7 @@ You need the following prerequisites to complete the steps in this guide:
 
 To get started, fork the IoT Central CI/CD GitHub repository and then clone your fork to your local machine:
 
-1. To fork the Git Hub repository, open the [IoT Central CI/CD GitHub repository](https://github.com/Azure/iot-central-CICD-sample) and select **Fork**.
+1. To fork the GitHub repository, open the [IoT Central CI/CD GitHub repository](https://github.com/Azure/iot-central-CICD-sample) and select **Fork**.
 
 1. Clone your fork of the repository to your local machine by opening a console or bash window and running the following command.
 
@@ -338,7 +338,7 @@ Now configure the pipeline to push configuration changes to your IoT Central app
     ```
 
 1. Select **Save and run**.
-1. The YAML file is saved to your Git Hub repository, so you need to provide a commit message and then select **Save and run** again.
+1. The YAML file is saved to your GitHub repository, so you need to provide a commit message and then select **Save and run** again.
 
 Your pipeline is queued. It may take a few minutes before it runs.
 

articles/service-fabric/service-fabric-containers-overview.md

@@ -41,9 +41,13 @@ Compared to virtual machines, containers have the following advantages:
 * **Portability**: A containerized application image can be ported to run in the cloud, on premises, inside virtual machines, or directly on physical machines.
 * **Resource governance**: A container can limit the physical resources that it can consume on its host.
 
-### Container types and supported environments
+## Service Fabric support for containers
+
+Service Fabric supports the deployment of Docker containers on Linux, and Windows Server containers on Windows Server 2016 and later, along with support for Hyper-V isolation mode.
 
-Service Fabric supports containers on both Linux and Windows, and supports Hyper-V isolation mode on Windows.
+Container runtimes compatible with ServiceFabric:
+- Mirantis Container Runtime
+- Moby
 
 #### Docker containers on Linux
 
@@ -70,10 +74,6 @@ Here are typical examples where a container is a good choice:
 
 * **Reduce impact of "noisy neighbors" services**: You can use the resource governance ability of containers to restrict the resources that a service uses on a host. If services might consume many resources and affect the performance of others (such as a long-running, query-like operation), consider putting these services into containers that have resource governance.
 
-## Service Fabric support for containers
-
-Service Fabric supports the deployment of Docker containers on Linux, and Windows Server containers on Windows Server 2016 and later, along with support for Hyper-V isolation mode.
-
 > [!NOTE]
 > A Service Fabric cluster is single tenant by design and hosted applications are considered **trusted**. If you are considering hosting **untrusted applications**, please see [Hosting untrusted applications in a Service Fabric cluster](service-fabric-best-practices-security.md#hosting-untrusted-applications-in-a-service-fabric-cluster).