Merge pull request #79776 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/active-directory-b2c/active-directory-b2c-reference-spa.md

@@ -15,7 +15,7 @@ ms.subservice: B2C
 
 # Single-page sign in using the OAuth 2.0 implicit flow in Azure Active Directory B2C
 
-Many modern applications have a single-page app front end that primarily is written in JavaScript. Often, the app is written by using a framework like AngularJS, Ember.js, or Durandal. Single-page apps and other JavaScript apps that run primarily in a browser have some additional challenges for authentication:
+Many modern applications have a single-page app front end that primarily is written in JavaScript. Often, the app is written by using a framework like React, Angular or Vue.js. Single-page apps and other JavaScript apps that run primarily in a browser have some additional challenges for authentication:
 
 - The security characteristics of these apps are different from traditional server-based web applications.
 - Many authorization servers and identity providers do not support cross-origin resource sharing (CORS) requests.

articles/active-directory/develop/msal-net-instantiate-confidential-client-config-options.md

@@ -59,12 +59,12 @@ An ASP.NET Core application configuration is described in an *appsettings.json*
 }
 ```
 
-Starting in MSAL.NET v3.x, you can configure your confidential client application from the config file. The classes related to the app configuration are located in the `Microsoft.Identity.Client.AppConfig` namespace.
+Starting in MSAL.NET v3.x, you can configure your confidential client application from the config file.
 
-In the class where you want configure and instantiate your application, you need to declare a `ConfidentialClientApplicationOptions` object.  Bind the configuration read from the source (including the appconfig.json file) to the instance of the application options:
+In the class where you want configure and instantiate your application, you need to declare a `ConfidentialClientApplicationOptions` object.  Bind the configuration read from the source (including the appconfig.json file) to the instance of the application options, using the `IConfigurationRoot.Bind()` method from the [Microsoft.Extensions.Configuration.Binder nuget package](https://www.nuget.org/packages/Microsoft.Extensions.Configuration.Binder):
 
 ```csharp
-using Microsoft.Identity.Client.AppConfig;
+using Microsoft.Identity.Client;
 
 private ConfidentialClientApplicationOptions _applicationOptions;
 _applicationOptions = new ConfidentialClientApplicationOptions();

articles/active-directory/devices/overview.md

@@ -30,7 +30,7 @@ In a mobile-first, cloud-first world, Azure Active Directory (Azure AD) enables
 
 Through devices in Azure AD, your users are getting access to your corporate assets. To protect your corporate assets, as an IT administrator, you want to manage these devices identities. This enables you to make sure that your users are accessing your resources from devices that meet your standards for security and compliance.
 
-Device identity management is also the foundation for [device-based Conditional Access](../conditional-access/require-managed-devices.md). With device-based Conditional Access, you can ensure that access to resources in your environment is only possible with managed devices.
+Device identity management is also the foundation for [device-based conditional access](../conditional-access/require-managed-devices.md). With device-based conditional access, you can ensure that access to resources in your environment is only possible with managed devices.
 
 ## Getting devices in Azure AD
 
@@ -41,7 +41,7 @@ To get a device in Azure AD, you have two options:
 
 **Registering** a device to Azure AD enables you to manage a device’s identity. When a device is registered, Azure AD device registration provides the device with an identity that is used to authenticate the device when a user signs-in to Azure AD. You can use the identity to enable or disable a device.
 
-When combined with a mobile device management(MDM) solution such as Microsoft Intune, the device attributes in Azure AD are updated with additional information about the device. This allows you to create Conditional Access rules that enforce access from devices to meet your standards for security and compliance. For more information on enrolling devices in Microsoft Intune, see [What is device enrollment?](https://docs.microsoft.com/intune/device-enrollment)
+When combined with a mobile device management(MDM) solution such as Microsoft Intune, the device attributes in Azure AD are updated with additional information about the device. This allows you to create conditional access rules that enforce access from devices to meet your standards for security and compliance. For more information on enrolling devices in Microsoft Intune, see [What is device enrollment?](https://docs.microsoft.com/intune/device-enrollment)
 
 **Joining** a device is an extension to registering a device. This means, it provides you with all the benefits of registering a device and in addition to this, it also changes the local state of a device. Changing the local state enables your users to sign-in to a device using an organizational work or school account instead of a personal account.
 
@@ -68,6 +68,7 @@ The goal of Azure AD joined devices is to simplify:
 - Windows deployments of work-owned devices
 - Access to organizational apps and resources from any Windows device
 - Cloud-based management of work-owned devices
+- Users to sign in to their devices with their Azure AD or synced Active Directory work or school accounts.
 
 ![Azure AD registered devices](./media/overview/02.png)
 
@@ -134,12 +135,10 @@ As a rule of a thumb, you should use:
 - Azure AD joined devices:
    - For devices that are owned by your organization
    - For devices that are **not** joined to an on-premises AD
-   - To manually register devices with Azure AD
    - To change the local state of a device
 - Hybrid Azure AD joined devices for devices that are joined to an on-premises AD
    - For devices that are owned by your organization
    - For devices that are joined to an on-premises AD
-   - To automatically register devices with Azure AD
    - To change the local state of a device
 
 ## License requirements
@@ -153,4 +152,4 @@ As a rule of a thumb, you should use:
    - Azure Active Directory registered Windows 10 devices, see [How to configure Azure Active Directory registered Windows 10 devices](../user-help/device-management-azuread-registered-devices-windows10-setup.md).
    - Azure Active Directory joined devices, see [How to plan your Azure Active Directory join implementation](azureadjoin-plan.md).
    - Hybrid Azure AD joined devices, see [How to plan your hybrid Azure Active Directory join implementation](hybrid-azuread-join-plan.md).
-- To learn more about device-based Conditional Access, see [Configure Azure Active Directory device-based Conditional Access policies](../conditional-access/require-managed-devices.md).
+- To learn more about device-based conditional access, see [Configure Azure Active Directory device-based conditional access policies](../conditional-access/require-managed-devices.md).

articles/app-service/app-service-web-tutorial-custom-domain.md

@@ -153,7 +153,7 @@ It might take some time for the new custom domain to be reflected in the app's *
 ![CNAME record added](./media/app-service-web-tutorial-custom-domain/cname-record-added.png)
 
 > [!NOTE]
-> A **Note Secure** label for your custom domain means that it's not yet bound to an SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add an SSL binding, see [Bind an existing custom SSL certificate to Azure App Service](app-service-web-tutorial-custom-ssl.md).
+> A **Not Secure** label for your custom domain means that it's not yet bound to an SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add an SSL binding, see [Bind an existing custom SSL certificate to Azure App Service](app-service-web-tutorial-custom-ssl.md).
 
 If you missed a step or made a typo somewhere earlier, you see a verification error at the bottom of the page.
 

articles/azure-monitor/app/api-custom-events-metrics.md

@@ -244,8 +244,8 @@ namespace User.Namespace.Example01
 ## TrackMetric
 
 > [!NOTE]
-> Microsoft.ApplicationInsights.TelemetryClient.TrackMetric is deprecated in the .NET SDK. Metrics should always be pre-aggregated across a time period before being sent. Use one of the GetMetric(..) overloads to get a metric object for accessing SDK pre-aggregation capabilities. If you are implementing your own pre-aggregation logic, you can 
-use the Track(ITelemetry metricTelemetry) method to send the resulting aggregates. If your application requires sending a separate telemetry item at every occasion without aggregation across time, you likely have a use case for event telemetry; see TelemetryClient.TrackEvent 
+> Microsoft.ApplicationInsights.TelemetryClient.TrackMetric is not the preferred method for sending metrics. Metrics should always be pre-aggregated across a time period before being sent. Use one of the GetMetric(..) overloads to get a metric object for accessing SDK pre-aggregation capabilities. If you are implementing your own pre-aggregation logic, you can 
+use the TrackMetric() method to send the resulting aggregates. If your application requires sending a separate telemetry item at every occasion without aggregation across time, you likely have a use case for event telemetry; see TelemetryClient.TrackEvent 
 (Microsoft.ApplicationInsights.DataContracts.EventTelemetry).
 
 Application Insights can chart metrics that are not attached to particular events. For example, you could monitor a queue length at regular intervals. With metrics, the individual measurements are of less interest than the variations and trends, and so statistical charts are useful.

articles/azure-monitor/app/asp-net-core.md

@@ -54,7 +54,7 @@ The [Application Insights SDK (Software Development Kit) for ASP.NET Core](https
 
     ```xml
         <ItemGroup>
-          <PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.6.1" />
+          <PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.7.0" />
         </ItemGroup>
     ```
 

articles/azure-resource-manager/resource-group-lock-resources.md

@@ -147,7 +147,7 @@ To lock a resource group, provide the name of the resource group.
 New-AzResourceLock -LockName LockGroup -LockLevel CanNotDelete -ResourceGroupName exampleresourcegroup
 ```
 
-To get information about a lock, use [Get-​Azure​Rm​Resource​Lock](/powershell/module/az.resources/get-azresourcelock). To get all the locks in your subscription, use:
+To get information about a lock, use [Get-AzResourceLock](/powershell/module/az.resources/get-azresourcelock). To get all the locks in your subscription, use:
 
 ```azurepowershell-interactive
 Get-AzResourceLock

articles/cosmos-db/cassandra-support.md

@@ -152,7 +152,7 @@ foreach (string key in insertResult.Info.IncomingPayload)
 
 ## Consistency mapping 
 
-Azure Cosmos DB Cassandra API provides choice of consistency for read operations.  The consistency mapping is detailed [here[(https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels-across-apis#cassandra-mapping).
+Azure Cosmos DB Cassandra API provides choice of consistency for read operations.  The consistency mapping is detailed [here[(https://docs.microsoft.com/azure/cosmos-db/consistency-levels-across-apis#cassandra-mapping).
 
 ## Permission and role management
 

articles/dev-spaces/how-dev-spaces-works.md

@@ -206,7 +206,7 @@ The `up` command uploads your application source files and other artifacts neede
 1. Builds the container for your application.
 1. Deploys your application to the dev space.
 1. Creates a publicly accessible DNS name for your application endpoint if configured.
-1. Uses *port-forward* to provide access to your application endpoint using http://locahost.
+1. Uses *port-forward* to provide access to your application endpoint using http://localhost.
 1. Forwards stdout and stderr to the client-side tooling.
 
 
@@ -441,4 +441,4 @@ To get started with team development, see the following how-to articles:
 
 
 
-[supported-regions]: about.md#supported-regions-and-configurations
+[supported-regions]: about.md#supported-regions-and-configurations

articles/iot-edge/tutorial-machine-learning-edge-02-prepare-environment.md

@@ -56,7 +56,7 @@ The DevVM directory contains the files needed to create an Azure virtual machine
 1. Open Powershell as an administrator and navigate to the directory where you downloaded the code. We will refer to the root directory for your source as `<srcdir>`.
 
     ```powershell
-    cd \<srcdir\>\IoTEdgeAndMlSample\DevVM
+    cd <srcdir>\IoTEdgeAndMlSample\DevVM
     ```
 
 2. Run the following command to allow execution of scripts. Choose **Yes to All** when prompted.
@@ -137,7 +137,7 @@ Now that you have connected to the development machine, add some useful extensio
 3. Run the script.
 
     ```powershell
-    .\\Enable-CodeExtensions.ps1
+    .\Enable-CodeExtensions.ps1
     ```
 
 4. The script will run for a few minutes installing VS code extensions: