Merge pull request #79689 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/automation/tutorial-configure-servers-desired-state.md

@@ -165,7 +165,7 @@ or the Az cmdlets.
 > so the node is no longer connecting to the service.
 > This does not effect the configuration that is currently applied to the node.
 > To remove the current configuration, use the
-> [PowerShell](https://docs.microsoft.com/en-us/powershell/module/psdesiredstateconfiguration/remove-dscconfigurationdocument?view=powershell-5.1)
+> [PowerShell](https://docs.microsoft.com/powershell/module/psdesiredstateconfiguration/remove-dscconfigurationdocument?view=powershell-5.1)
 > or delete the local configuration file
 > (this is the only option for Linux nodes).
 
@@ -180,7 +180,7 @@ In the Node view that opens, click **Unregister**.
 
 To unregister a node from Azure Automation State Configuration service using PowerShell,
 follow the documentation for the cmdlet
-[Unregister-AzAutomationDscNode](https://docs.microsoft.com/en-us/powershell/module/az.automation/unregister-azautomationdscnode?view=azps-2.0.0).
+[Unregister-AzAutomationDscNode](https://docs.microsoft.com/powershell/module/az.automation/unregister-azautomationdscnode?view=azps-2.0.0).
 
 ## Next steps
 

articles/container-instances/container-instances-managed-identity.md

@@ -150,7 +150,7 @@ az container exec --resource-group myResourceGroup --name mycontainer --exec-com
 Run the following commands in the bash shell in the container. To get an access token to use Azure Active Directory to authenticate to Key Vault, run the following command:
 
 ```bash
-curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https%3A%2F%2Fvault.azure.net%2F' -H Metadata:true -s
+curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https%3A%2F%2Fvault.azure.net' -H Metadata:true -s
 ```
 
 Output:

articles/databox-online/data-box-edge-overview.md

@@ -31,7 +31,7 @@ Azure Data Box Edge is an AI-enabled edge computing device with network data tra
     - Analyze and react to IoT Events. 
 
 - **Inference Azure Machine Learning** - With Data Box Edge, you can run Machine Learning (ML) models to get quick results that can be acted on before the data is sent to the cloud. The full data set can be transferred to continue to retrain and improve your ML models. For more information on how to use the Azure ML hardware accelerated models on the Databox Edge device, see 
-[Deploy Azure ML hardware accelerated models on Databox Edge](https://docs.microsoft.com/en-us/azure/machine-learning/service/how-to-deploy-fpga-web-service#deploy-to-a-local-edge-server).
+[Deploy Azure ML hardware accelerated models on Databox Edge](https://docs.microsoft.com/azure/machine-learning/service/how-to-deploy-fpga-web-service#deploy-to-a-local-edge-server).
 
 - **Transfer data over network to Azure** - Use Data Box Edge to easily and quickly transfer data to Azure to enable further compute and analytics or for archival purposes. 
 

includes/active-directory-service-limits-include.md

@@ -23,4 +23,4 @@ Here are the usage constraints and other service limits for the Azure Active Dir
 | Access Panel |<ul><li>There's no limit to the number of applications that can be seen in the Access Panel per user. This applies to users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.</li><li>A maximum of 10 app tiles can be seen in the Access Panel for each user. This limit applies to users who are assigned licenses for Free or Azure AD Basic editions of Azure Active Directory. Examples of app tiles include Box, Salesforce, or Dropbox. This limit doesn't apply to administrator accounts.</li></ul> |
 | Reports | A maximum of 1,000 rows can be viewed or downloaded in any report. Any additional data is truncated. |
 | Administrative units | An object can be a member of no more than 30 administrative units. |
-| Admin roles and permissions | <ul><li>A group cannot be added as an [owner](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/users-default-permissions?context=azure/active-directory/users-groups-roles/context/ugr-context#object-ownership).</li><li>A group cannot be assigned to a [role](https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles).</li><li>Users’ ability to read other users’ directory information cannot be restricted outside of the tenant-wide switch to disable all non-admin users’ access to all directory information (not recommended). More information on default permissions [here](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/users-default-permissions?context=azure/active-directory/users-groups-roles/context/ugr-context#to-restrict-the-default-permissions-for-member-users).</li><li>It may take up to 15 minutes or signing out/signing in before admin role membership additions and revocations take effect.</li></ul> |
+| Admin roles and permissions | <ul><li>A group cannot be added as an [owner](https://docs.microsoft.com/azure/active-directory/fundamentals/users-default-permissions?context=azure/active-directory/users-groups-roles/context/ugr-context#object-ownership).</li><li>A group cannot be assigned to a [role](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles).</li><li>Users’ ability to read other users’ directory information cannot be restricted outside of the tenant-wide switch to disable all non-admin users’ access to all directory information (not recommended). More information on default permissions [here](https://docs.microsoft.com/azure/active-directory/fundamentals/users-default-permissions?context=azure/active-directory/users-groups-roles/context/ugr-context#to-restrict-the-default-permissions-for-member-users).</li><li>It may take up to 15 minutes or signing out/signing in before admin role membership additions and revocations take effect.</li></ul> |