Merge pull request #222684 from MicrosoftDocs/main

12/30 PM Publish

Author: huypub

articles/active-directory-b2c/TOC.yml

@@ -70,13 +70,13 @@
     items:
       - name: Global identity solutions
         href: azure-ad-b2c-global-identity-solutions.md
-      - name: Funnel-based design considerations
+      - name: Funnel-based design
         href: azure-ad-b2c-global-identity-funnel-based-design.md
-      - name: Region-based design considerations
+      - name: Region-based design
         href: azure-ad-b2c-global-identity-region-based-design.md
       - name: Funnel-based proof of concept 
         href: azure-ad-b2c-global-identity-proof-of-concept-funnel.md
-      - name: Regional-based proof of concept 
+      - name: Region-based proof of concept 
         href: azure-ad-b2c-global-identity-proof-of-concept-regional.md
   - name: Azure AD B2C best practices
     href: best-practices.md

articles/active-directory-b2c/azure-ad-b2c-global-identity-funnel-based-design.md

@@ -22,14 +22,14 @@ The designs account for:
 
 * Local Account sign up and sign in
 * Federated account sign up and sign in
-* Authenticating local accounts for users signing in from outside their registered region, supported by cross tenant API based authentication.
+* Authenticating local accounts for users signing in from outside their registered region, supported by cross tenant API based authentication
 * Authenticating federated accounts for users signing in from outside their registered region, supported by cross tenant API based look up
 * Prevents sign up from multiple different regions
 * Applications in each region have a single endpoint to connect with
 
 ## Local account sign-in use cases
 
-The following use cases are typical in a global Azure AD B2C environment. The local account use cases also cover accounts where the user travels. Each provides a diagram and workflow steps for each use case.
+The following use cases are typical in a global Azure AD B2C environment. The local account use cases also cover accounts where the user travels. We provide a diagram and workflow steps for each use case.
 
 ### Local user sign-up
 
@@ -99,8 +99,7 @@ This use case demonstrates how a user can travel across regions and maintain the
 
 1. The EMEA Azure AD B2C tenant performs an Azure AD ROPC flow against the NOAM Azure AD B2C tenant to verify credentials.
    >[!NOTE]
-   >This call will also fetch a token for the user to perform a Graph API call.
-   The EMEA Azure AD B2C tenant performs a Graph API call to the NOAM Azure AD B2C tenant to fetch the user's profile. This call is authenticated by the access token for Graph API acquired in the last step.
+   >This call will also fetch a token for the user to perform a Graph API call. The EMEA Azure AD B2C tenant performs a Graph API call to the NOAM Azure AD B2C tenant to fetch the user's profile. This call is authenticated by the access token for Graph API acquired in the last step.
 
 1. The regional tenant issues a token back to the funnel tenant.
 
@@ -312,6 +311,6 @@ This use case demonstrates how non-local users are able to perform account linki
 
 - [Build a global identity solution with region-based approach](azure-ad-b2c-global-identity-region-based-design.md)
 
-- [Azure AD B2C global identity proof of concept regional-based configuration](azure-ad-b2c-global-identity-proof-of-concept-regional.md)
+- [Azure AD B2C global identity proof of concept region-based configuration](azure-ad-b2c-global-identity-proof-of-concept-regional.md)
 
 - [Azure AD B2C global identity proof of concept funnel-based configuration](azure-ad-b2c-global-identity-proof-of-concept-funnel.md)

articles/active-directory-b2c/azure-ad-b2c-global-identity-proof-of-concept-regional.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Active Directory B2C global identity framework proof of concept for regional based configuration
+title: Azure Active Directory B2C global identity framework proof of concept for region-based configuration
 description: Learn how to create a proof of concept regional based approach for Azure AD B2C to provide customer identity and access management for global customers.
 services: active-directory-b2c
 author: gargi-sinha
@@ -13,11 +13,11 @@ ms.author: gasinh
 ms.subservice: B2C
 ---
 
-# Azure Active Directory B2C global identity framework proof of concept regional based configuration
+# Azure Active Directory B2C global identity framework proof of concept for region-based configuration
 
-The following section describes how to create proof of concept implementations for regional-based orchestration. The completed Azure Active Directory B2C (Azure AD B2C) custom policies can be found [here](https://github.com/azure-ad-b2c/samples/tree/master/policies/global-architecture-model/region-based-approach).
+The following section describes how to create proof of concept implementations for region-based orchestration. The completed Azure Active Directory B2C (Azure AD B2C) custom policies can be found [here](https://github.com/azure-ad-b2c/samples/tree/master/policies/global-architecture-model/region-based-approach).
 
-## Regional-based approach
+## Region-based approach
 
 Each regional Azure AD B2C tenant will require an Azure AD B2C Custom policy, which contains the following capabilities:
 

articles/active-directory-b2c/azure-ad-b2c-global-identity-region-based-design.md

@@ -108,9 +108,7 @@ This use case demonstrates how a user can reset their password when they are wit
 
 ![Screenshot shows the local user forgot password flow.](media/azure-ad-b2c-global-identity-regional-design/local-user-forgot-password.png)
 
-1. User from EMEA attempts to sign in at **myapp.fr**.
-
-   If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
+1. User from EMEA attempts to sign in at **myapp.fr**. If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
 
 1. The user arrives at the EMEA Azure AD B2C tenant and selects **forgot password**. The user enters and verifies their email.
 
@@ -128,9 +126,7 @@ This use case demonstrates how a user can reset their password when they're trav
 
 ![Screenshot shows the traveling user forgot password flow.](media/azure-ad-b2c-global-identity-regional-design/traveling-user-forgot-password.png)
 
-1. User from NOAM attempts to sign in at **myapp.fr**, since they are on holiday in France.
-
-   If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
+1. User from NOAM attempts to sign in at **myapp.fr**, since they are on holiday in France. If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
 
 1. The user arrives at the EMEA Azure AD B2C tenant and selects **forgot password**. The user enters and verifies their email.
 
@@ -204,9 +200,7 @@ This use case demonstrates how a user from their local region signs into the ser
 
 ![Screenshot shows the sign in flow.](media/azure-ad-b2c-global-identity-regional-design/social-account-sign-in.png)
 
-1. User from EMEA attempts to sign in at **myapp.fr**.
-
-   If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
+1. User from EMEA attempts to sign in at **myapp.fr**. If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
 
 1. User lands at the EMEA tenant.
 
@@ -222,15 +216,13 @@ This scenario demonstrates how a user located away from the region in which they
 
 ![Screenshot shows the sign in for traveling user flow.](media/azure-ad-b2c-global-identity-regional-design/traveling-user-social-account-sign-in.png)
 
-1. User from NOAM attempts to sign in at **myapp.fr**.
-
-   If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
+1. User from NOAM attempts to sign in at **myapp.fr**. If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
 
 1. User lands at the EMEA tenant.
 
 1. User selects to sign in with a federated identity provider.
 
-    >[!NOTE]
+   >[!NOTE]
    >Use the same App Id from the App Registration at the Social IdP across all Azure AD B2C regional tenants. This ensures that the ID coming back from the Social IdP is always the same.
 
 1. Perform a lookup into the global lookup table and determine the user's federated ID is registered in NOAM.
@@ -245,9 +237,7 @@ This scenario demonstrates how users will be able to perform account linking whe
 
 ![Screenshot shows the merge/link accounts flow.](media/azure-ad-b2c-global-identity-regional-design/merge-link-account.png)
 
-1. User from EMEA attempts to sign in at **myapp.fr**.
-
-   If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
+1. User from EMEA attempts to sign in at **myapp.fr**. If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
 
 1. User lands at the EMEA tenant.
 
@@ -269,15 +259,13 @@ This scenario demonstrates how users will be able to perform  account linking wh
 
 ![Screenshot shows the traveling user merge/link accounts flow.](media/azure-ad-b2c-global-identity-regional-design/traveling-user-merge-link-account.png)
 
-1. User from NOAM attempts to sign in at **myapp.fr**.
-
-   If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
+1. User from NOAM attempts to sign in at **myapp.fr**. If the user isn't being sent to their local hostname, the traffic manager will enforce a redirect.
 
 1. User lands at the EMEA tenant.
 
 1. User selects to sign in with a federated identity provider/social IdP.
 
-1. A lookup is performed into the global lookup table for the ID     returned from the federated IdP.
+1. A lookup is performed into the global lookup table for the ID returned from the federated IdP.
 
 1. Where the ID doesn't exist, and the email from the federated IdP exists in another region, it's a traveling user account linking scenario.
 

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

@@ -44,8 +44,7 @@ The [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Micro
 * **IDE**: Visual Studio, Visual Studio Code, or command line
 
 > [!NOTE]
-> - ASP.NET Core 6.0 requires [Application Insights 2.19.0](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/2.18.0) or later
-> - ASP.NET Core 3.1 requires [Application Insights 2.8.0](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/2.8.0) or later
+> - ASP.NET Core 6.0 requires [Application Insights 2.19.0](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/2.19.0) or later
 
 ## Prerequisites
 
@@ -86,7 +85,7 @@ For Visual Studio for Mac, use the [manual guidance](#enable-application-insight
 
 2. Add `AddApplicationInsightsTelemetry()` to your `startup.cs` or `program.cs` class (depending on your .NET Core version)
 
-    ### [ASP.NET Core 6.0](#tab/netcore6)
+    ### [ASP.NET Core 6 and later](#tab/netcorenew)
 
     Add `builder.Services.AddApplicationInsightsTelemetry();` after the `WebApplication.CreateBuilder()` method in your `Program` class, as in this example:
 
@@ -103,7 +102,7 @@ For Visual Studio for Mac, use the [manual guidance](#enable-application-insight
     var app = builder.Build();
     ```
 
-    ### [ASP.NET Core 3.1](#tab/netcore3)
+    ### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
     Add `services.AddApplicationInsightsTelemetry();` to the `ConfigureServices()` method in your `Startup` class, as in this example:
 
@@ -238,7 +237,7 @@ You can customize the Application Insights SDK for ASP.NET Core to change the de
 
 You can modify a few common settings by passing `ApplicationInsightsServiceOptions` to `AddApplicationInsightsTelemetry`, as in this example:
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 var builder = WebApplication.CreateBuilder(args);
@@ -255,7 +254,7 @@ builder.Services.AddApplicationInsightsTelemetry(aiOptions);
 var app = builder.Build();
 ```
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 public void ConfigureServices(IServiceCollection services)
@@ -320,7 +319,7 @@ When you want to enrich telemetry with additional information, use [telemetry in
 
 Add any new `TelemetryInitializer` to the `DependencyInjection` container as shown in the following code. The SDK automatically picks up any `TelemetryInitializer` that's added to the `DependencyInjection` container.
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 var builder = WebApplication.CreateBuilder(args);
@@ -333,7 +332,7 @@ var app = builder.Build();
 > [!NOTE]
 > `builder.Services.AddSingleton<ITelemetryInitializer, MyCustomTelemetryInitializer>();` works for simple initializers. For others, the following is required: `builder.Services.AddSingleton(new MyCustomTelemetryInitializer() { fieldName = "myfieldName" });`
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 public void ConfigureServices(IServiceCollection services)
@@ -351,7 +350,7 @@ public void ConfigureServices(IServiceCollection services)
 
 By default, telemetry initializers are present. To remove all or specific telemetry initializers, use the following sample code *after* calling `AddApplicationInsightsTelemetry()`.
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 var builder = WebApplication.CreateBuilder(args);
@@ -373,7 +372,7 @@ builder.Services.RemoveAll(typeof(ITelemetryInitializer));
 var app = builder.Build();
 ```
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 public void ConfigureServices(IServiceCollection services)
@@ -400,7 +399,7 @@ public void ConfigureServices(IServiceCollection services)
 
 You can add custom telemetry processors to `TelemetryConfiguration` by using the extension method `AddApplicationInsightsTelemetryProcessor` on `IServiceCollection`. You use telemetry processors in [advanced filtering scenarios](./api-filtering-sampling.md#itelemetryprocessor-and-itelemetryinitializer). Use the following example.
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 var builder = WebApplication.CreateBuilder(args);
@@ -415,7 +414,7 @@ builder.Services.AddApplicationInsightsTelemetryProcessor<MySecondCustomTelemetr
 var app = builder.Build();
 ```
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 public void ConfigureServices(IServiceCollection services)
@@ -447,7 +446,7 @@ By default, the following automatic-collection modules are enabled. These module
 
 To configure any default `TelemetryModule`, use the extension method `ConfigureTelemetryModule<T>` on `IServiceCollection`, as shown in the following example.
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 using Microsoft.ApplicationInsights.DependencyCollector;
@@ -481,7 +480,7 @@ if (performanceCounterService != null)
 var app = builder.Build();
 ```
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 using Microsoft.ApplicationInsights.DependencyCollector;
@@ -524,7 +523,7 @@ In versions 2.12.2 and later, [`ApplicationInsightsServiceOptions`](#using-appli
 
 The default [telemetry channel](./telemetry-channels.md) is `ServerTelemetryChannel`. The following example shows how to override it.
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 using Microsoft.ApplicationInsights.Channel;
@@ -540,7 +539,7 @@ builder.Services.AddApplicationInsightsTelemetry();
 var app = builder.Build();
 ```
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 using Microsoft.ApplicationInsights.Channel;
@@ -564,7 +563,7 @@ public void ConfigureServices(IServiceCollection services)
 
 If you want to disable telemetry conditionally and dynamically, you can resolve the `TelemetryConfiguration` instance with an ASP.NET Core dependency injection container anywhere in your code and set the `DisableTelemetry` flag on it.
 
-### [ASP.NET Core 6.0](#tab/netcore6)
+### [ASP.NET Core 6 and later](#tab/netcorenew)
 
 ```csharp
 var builder = WebApplication.CreateBuilder(args);
@@ -577,7 +576,7 @@ builder.Services.Configure<TelemetryConfiguration>(x => x.DisableTelemetry = tru
 var app = builder.Build();
 ```
 
-### [ASP.NET Core 3.1](#tab/netcore3)
+### [ASP.NET Core 5 and earlier](#tab/netcoreold)
 
 ```csharp
 public void ConfigureServices(IServiceCollection services)

articles/azure-monitor/app/create-new-resource.md

@@ -2,7 +2,7 @@
 title: Create a new Azure Application Insights resource | Microsoft Docs
 description: Manually set up Application Insights monitoring for a new live application.
 ms.topic: conceptual
-ms.date: 11/15/2022
+ms.date: 01/28/2023
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ms.reviewer: dalek
 ---

articles/azure-monitor/toc.yml

@@ -728,8 +728,6 @@ items:
         href: app/opentelemetry-enable.md?tabs=python
       - name: FAQ
         href: /azure/azure-monitor/faq#opentelemetry
-    - name: Create a resource (classic)
-      href: app/create-new-resource.md
     - name: Create a resource (workspace-based)
       href: app/create-workspace-resource.md
     - name: Migrate to a workspace-based resource
@@ -1664,7 +1662,9 @@ items:
           - name: Key Vault Analytics (deprecated)
             href: insights/azure-key-vault-deprecated.md
     - name: Application Insights Java 2.x
-      href: ./app/deprecated-java-2x.md    
+      href: ./app/deprecated-java-2x.md
+    - name: Create a new App Insights resource (classic)
+      href: app/create-new-resource.md
     - name: Classic autoscale & metrics API
       href: ./essentials/classic-api-retirement-metrics-autoscale.md
     - name: NULL values in exported metrics