Update Learning Path

- Rename Azure Active Directory to Microsoft Entra ID - Add Cold storage tier
arvigeus · May 16, 2024 · 4768677 · 4768677
1 parent 82aea29
commit 4768677
Show file tree

Hide file tree

Showing 21 changed files with 222 additions and 195 deletions.
diff --git a/Case Studies/AD Application Manifest.md b/Case Studies/AD Application Manifest.md
diff --git a/Exercises/Implement interactive authentication by using MSAL.NET/README.md b/Exercises/Implement interactive authentication by using MSAL.NET/README.md
@@ -14,19 +14,19 @@ In this exercise you learn how to perform the following actions:
 ## Register a new application
 
 1. Sign in to the portal: <https://portal.azure.com>
-1. Search for and select Azure Active Directory.
-1. Under Manage, select App registrations > New registration.
-1. When the Register an application page appears, enter your application's registration information:
+1. Search for and select **Microsoft Entra ID**.
+1. Under Manage, select **App registrations** > **New registration**.
+1. When the **Register an application** page appears, enter your application's registration information:
 
-   | Field                   | Value                                                                                                |
-   | ----------------------- | ---------------------------------------------------------------------------------------------------- |
-   | Name                    | az204appreg                                                                                          |
-   | Supported account types | Select Accounts in this organizational directory only                                                |
-   | Redirect URI (optional) | Select Public client/native (mobile & desktop) and enter <http://localhost> in the box to the right. |
+   | Field                   | Value                                                                                                    |
+   | ----------------------- | -------------------------------------------------------------------------------------------------------- |
+   | Name                    | `az204appreg`                                                                                            |
+   | Supported account types | Select **Accounts in this organizational directory only**                                                |
+   | Redirect URI (optional) | Select **Public client/native (mobile & desktop)** and enter `http://localhost` in the box to the right. |
 
 1. Select **Register**.
 
-Azure Active Directory assigns a unique application (client) ID to your app, and you're taken to your application's **Overview** page.
+Microsoft Entra ID assigns a unique application (client) ID to your app, and you're taken to your application's **Overview** page.
 
 ## Set up the console application
 
@@ -56,7 +56,7 @@ In this section, you add the necessary packages and code to the project.
 
 ### Add packages and using statements
 
-1. Add the Microsoft.Identity.Client package to the project in a terminal in Visual Studio Code.
+1. Add the `Microsoft.Identity.Client` package to the project in a terminal in Visual Studio Code.
 
    ```sh
    dotnet add package Microsoft.Identity.Client
@@ -94,10 +94,10 @@ In this section, you add the necessary packages and code to the project.
        .Build();
    ```
 
-   | Code           | Description                                                                                                                                            |
-   | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-   | .Create        | Creates a PublicClientApplicationBuilder from a clientID.                                                                                              |
-   | .WithAuthority | Adds a known Authority corresponding to an ADFS server. In the code we're specifying the Public cloud, and using the tenant for the app we registered. |
+   | Code             | Description                                                                                                                                            |
+   | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+   | `.Create`        | Creates a `PublicClientApplicationBuilder` from a clientID.                                                                                            |
+   | `.WithAuthority` | Adds a known Authority corresponding to an ADFS server. In the code we're specifying the Public cloud, and using the tenant for the app we registered. |
 
 ### Acquire a token
 

diff --git a/Learning Path/API Management.md b/Learning Path/API Management.md
@@ -46,7 +46,7 @@ Groups are used to manage the visibility of products to developers. API Manageme
 - **Developers** - Authenticated developer portal users that build applications using your APIs. Developers are granted access to the developer portal and build applications that call the operations of an API.
 - **Guests** - Unauthenticated developer portal users. They can be granted certain read-only access, like the ability to view APIs but not call them.
 
-In addition to these system groups, administrators can create custom groups or use external groups in associated Azure Active Directory tenants.
+In addition to these system groups, administrators can create custom groups or use external groups in associated Microsoft Entra tenants.
 
 #### Developers
 
@@ -400,7 +400,7 @@ Every client certificate includes a thumbprint, which is a hash, calculated from
 
 ##### Check the thumbprint against certificates uploaded to API Management
 
-In the previous example, only one thumbprint would work so only one certificate would be validated. Usually, each customer or partner company would pass a different certificate with a different thumbprint. To support this scenario, obtain the certificates from your partners and use the Client certificates page in the Azure portal to upload them to the API Management resource. Then add this code to your policy:
+In the previous example, only one thumbprint would work so only one certificate would be validated. Usually, each customer or partner company would pass a different certificate with a different thumbprint. To support this scenario, obtain the certificates from your partners and use the **Client certificates** page in the Azure portal to upload them to the API Management resource. Then add this code to your policy:
 
 ```xml
 <choose>