Merge pull request #296400 from MicrosoftDocs/main

Publish to live, Sunday 4PM PST, 3/16

Author: JillGrant615

articles/azure-signalr/howto-use-managed-identity.md

@@ -80,6 +80,13 @@ After you add a [system-assigned identity](#add-a-system-assigned-identity) or [
 1. In the managed identity authentication settings, for **Audience in the issued token**, you can specify the target **resource**. The **resource** will become an `aud` claim in the obtained access token, which can be used as a part of validation in your upstream endpoints. The resource can be in one of the following formats:
 
    - Application (client) ID of the service principal.
+
+     When using Application (client) ID, the application has to be in the same tenant that the Azure SignalR resource is in. If your application is in a different tenant, please follow these steps:
+     1. [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/single-and-multi-tenant-apps) to convert your application to a multitenant application.
+     2. [Create an enterprise application from a multitenant application in Microsoft Entra ID](/entra/identity/enterprise-apps/create-service-principal-cross-tenant?pivots=admin-consent-url) to provision your application in the current tenant.
+     
+     Then you'll be able to find the enterprise application by clicking the "Or select from existing applications".
+   
    - Application ID URI of the service principal.
 
    > [!IMPORTANT]

includes/cdn-app-dev-prep.md

@@ -1,10 +1,12 @@
 ---
 author: zhangmanling
+ms.author: mazha
 ms.service: azure-cdn
 ms.topic: include
 ms.date: 11/21/2018
-ms.author: mazha
+ms.custom: include file
 ---
+
 ## Prerequisites
 Before writing CDN management code, you must do some preparation to enable the code to interact with the Azure Resource Manager. To do this preparation, you need to:
 
@@ -13,15 +15,15 @@ Before writing CDN management code, you must do some preparation to enable the c
 * Apply permissions to the resource group so that only authorized users from your Microsoft Entra tenant can interact with the CDN profile
 
 ### Creating the resource group
-1. Sign in to the [Azure Portal](https://portal.azure.com).
-2. Click **Create a resource**.
-3. Search for **Resource group** and in the Resource group pane, click **Create**.
+1. Sign in to the [Azure portal](https://portal.azure.com).
+2. Select **Create a resource**.
+3. Search for **Resource group** and in the Resource group pane, select **Create**.
 
     ![Creating a new resource group](./media/cdn-app-dev-prep/cdn-new-rg-1-include.png)
-3. Name your resource group *CdnConsoleTutorial*.  Select your subscription and choose a location near you.  If you wish, you can click the **Pin to dashboard** checkbox to pin the resource group to the dashboard in the portal.  Pinning makes it easier to find later.  After you've made your selections, click **Create**.
+3. Name your resource group *CdnConsoleTutorial*.  Select your subscription and choose a location near you.  If you wish, you can select the **Pin to dashboard** checkbox to pin the resource group to the dashboard in the portal.  Pinning makes it easier to find later.  After you've made your selections, select **Create**.
 
     ![Screenshot of the Resource group dialog box.](./media/cdn-app-dev-prep/cdn-new-rg-2-include.png)
-4. After the resource group is created, if you didn't pin it to your dashboard, you can find it by clicking **Browse**, then **Resource Groups**.  To open it, click the resource group.  Make a note of your **Subscription ID**. We need it later.
+4. After the resource group is created, if you didn't pin it to your dashboard, you can find it by clicking **Browse**, then **Resource Groups**.  To open it, select the resource group.  Make a note of your **Subscription ID**. We need it later.
 
     ![Screenshot of the C D N Console Tutorial section.](./media/cdn-app-dev-prep/cdn-subscription-id-include.png)
 
@@ -39,7 +41,6 @@ Creating a service principal consists of several steps, including creating a Mic
 >
 > When you get to the step [Assign the application to a role](../articles/active-directory/develop/howto-create-service-principal-portal.md#assign-a-role-to-the-application), use the resource group created earlier,  *CdnConsoleTutorial*, but instead of the **Reader** role, assign the **CDN Profile Contributor** role.  After you assign the application the **CDN Profile Contributor** role on your resource group, return to this tutorial. 
 >
->
 
 Once you've created your service principal and assigned the **CDN Profile Contributor** role, the **Users** blade for your resource group should look similar to the following image.
 
@@ -49,15 +50,13 @@ Once you've created your service principal and assigned the **CDN Profile Contri
 If, instead of a service principal, you'd rather have interactive individual user authentication, the process is similar to that for a service principal.  In fact, you need to follow the same procedure, but make a few minor changes.
 
 > [!IMPORTANT]
-> Only follow these next steps if you are choosing to use individual user authentication instead of a service principal.
->
->
+> Only follow these next steps if you're choosing to use individual user authentication instead of a service principal.
 
 1. When creating your application, instead of **Web Application**, choose **Native application**.
 
     ![Native application](./media/cdn-app-dev-prep/cdn-native-application-include.png)
-2. On the next page, you are prompted for a **redirect URI**.  The URI won't be validated, but remember what you entered. You need it later.
-3. There is no need to create a **client authentication key**.
+2. On the next page, you're prompted for a **redirect URI**.  The URI won't be validated, but remember what you entered. You need it later.
+3. There's no need to create a **client authentication key**.
 4. Instead of assigning a service principal to the **CDN Profile Contributor** role, we're going to assign individual users or groups.  In this example, you can see that I've assigned  *CDN Demo User* to the **CDN Profile Contributor** role.  
 
     ![Individual user access](./media/cdn-app-dev-prep/cdn-user-include.png)

includes/cdn-classic-retirement.md

@@ -1,13 +1,10 @@
 ---
- title: Azure CDN Standard from Microsoft (classic) retirement notice
- description: include file
- services: azure-cdn
- author: duongau
- ms.service: azure-cdn
- ms.topic: include
- ms.date: 1/21/2025
- ms.author: duau
- ms.custom: include file
+author: halkazwini
+ms.author: halkazwini
+ms.service: azure-cdn
+ms.topic: include
+ms.date: 1/21/2025
+ms.custom: include file
 ---
 
 > [!IMPORTANT]

includes/cdn-create-profile.md

@@ -1,12 +1,9 @@
 ---
-title: include file
-description: include file
-services: cdn
 author: SyntaxC4
+ms.author: cfowler
 ms.service: azure-cdn
 ms.topic: include
 ms.date: 04/06/2022
-ms.author: cfowler
 ms.custom: include file
 ---
 
@@ -41,4 +38,3 @@ A CDN profile is a container for CDN endpoints and specifies a pricing tier.
     :::image type="content" source="./media/cdn-create-profile/cdn-new-profile.png" alt-text="Input variables in Basics tab.":::
 
 1. Select **Review + Create** then **Create** to create the profile.
-

includes/cdn-limits.md

@@ -1,9 +1,10 @@
 ---
 author: mdgattuso
-ms.service: cdn
+ms.author: magattus
+ms.service: azure-cdn
 ms.topic: include
 ms.date: 07/31/2021    
-ms.author: magattus
+ms.custom: include file
 ---
 
 | Resource | Limit |
@@ -20,8 +21,6 @@ ms.author: magattus
 | Maximum requests per second per profile | 100,000 |
 | HTTP header size limit (per header) | 32 KB |
 
-*These two limits are only applicable to Azure CDN Standard from Microsoft (classic). If the traffic is not globally distributed and concentrated in one or two regions, or if a higher quota limit is needed, create an [Azure Support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). 
+*These two limits are only applicable to Azure CDN Standard from Microsoft (classic). If the traffic isn't globally distributed and concentrated in one or two regions, or if a higher quota limit is needed, create an [Azure Support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). 
 
 A Content Delivery Network subscription can contain one or more Content Delivery Network profiles. A Content Delivery Network profile can contain one or more Content Delivery Network endpoints. You might want to use multiple profiles to organize your Content Delivery Network endpoints by internet domain, web application, or some other criteria. 
-
-

includes/cdn-premium-feature.md

@@ -1,15 +1,11 @@
 ---
-title: include file
-description: include file
-services: cdn
-author: duongau
+author: halkazwini
+ms.author: halkazwini
 ms.service: azure-cdn
 ms.topic: include
 ms.date: 09/08/2023
-ms.author: duau
 ms.custom: include file
 ---
 
 > [!IMPORTANT]
-> This is a feature of **Azure CDN Premium from Edgio** only, to configure rules on **Azure CDN from Microsoft** please use the [Standard rules engine](../articles/cdn/cdn-standard-rules-engine-reference.md). Advanced rules are not available for **Azure CDN from Akamai**. For a full comparison of CDN features, see [Azure CDN product features](../articles/cdn/cdn-features.md). 
-> 
+> This is a feature of **Azure CDN Premium from Edgio** only, to configure rules on **Azure CDN from Microsoft** please use the [Standard rules engine](../articles/cdn/cdn-standard-rules-engine-reference.md). Advanced rules aren't available for **Azure CDN from Akamai**. For a full comparison of CDN features, see [Azure CDN product features](../articles/cdn/cdn-features.md). 

includes/cdn-verizon-only.md

@@ -1,12 +1,9 @@
 ---
-title: include file
-description: include file
-services: cdn
-author: duongau
+author: halkazwini
+ms.author: halkazwini
 ms.service: azure-cdn
 ms.topic: include
 ms.date: 10/29/2024
-ms.author: duau
 ms.custom: include file
 ---
 

includes/front-door-classic-retirement.md

@@ -1,13 +1,10 @@
 ---
- title: Azure Front Door (classic) retirement notice
- description: include file
- services: front-door
- author: duongau
- ms.service: front-door
- ms.topic: include
- ms.date: 03/18/2024
- ms.author: duau
- ms.custom: include file
+author: halkazwini
+ms.author: halkazwini
+ms.service: azure-frontdoor
+ms.topic: include
+ms.date: 03/18/2024
+ms.custom: include file
 ---
 > [!IMPORTANT]
-> Azure Front Door (classic) will be retired on **March 31, 2027**. To avoid any service disruption, it is important that you [**migrate your Azure Front Door (classic) profiles**](../articles/frontdoor/migrate-tier.md) to Azure Front Door Standard or Premium tier by March 2027. For more information, see [**Azure Front Door (classic) retirement**](https://azure.microsoft.com/updates/azure-front-door-classic-will-be-retired-on-31-march-2027/).
+> Azure Front Door (classic) will be retired on **March 31, 2027**. To avoid any service disruption, it's important that you [**migrate your Azure Front Door (classic) profiles**](../articles/frontdoor/migrate-tier.md) to Azure Front Door Standard or Premium tier by March 2027. For more information, see [**Azure Front Door (classic) retirement**](https://azure.microsoft.com/updates/azure-front-door-classic-will-be-retired-on-31-march-2027/).

includes/front-door-edge-locations-by-abbreviation.md

@@ -1,13 +1,10 @@
 ---
- title: include file
- description: include file
- services: frontdoor
- author: duongau
- ms.service: azure-frontdoor
- ms.topic: include
- ms.date: 06/01/2023
- ms.author: duau
- ms.custom: include file
+author: halkazwini
+ms.author: halkazwini
+ms.service: azure-frontdoor
+ms.topic: include
+ms.date: 06/01/2023
+ms.custom: include file
 ---
 
 | Abbreviation | Location | Region |

includes/front-door-edge-locations.md

@@ -1,18 +1,15 @@
 ---
- title: include file
- description: include file
- services: frontdoor
- author: duongau
- ms.service: azure-frontdoor
- ms.topic: include
- ms.date: 10/16/2023
- ms.author: duau
- ms.custom: include file
+author: halkazwini
+ms.author: halkazwini
+ms.service: azure-frontdoor
+ms.topic: include
+ms.date: 10/16/2023
+ms.custom: include file
 ---
 
 | Region | Cities |
 |--|--|
-| North America | Etobicoke, Canada (2)<br />Montreal, Canada<br />Vancouver, Canada (2)<br />Querétaro, Mexico (2)<br />Atlanta, GA, USA (3)<br />Boydton, VA, USA (2)<br />Chaska, MN, USA (2)<br /> Cheyenne, WY, USA (2)<br />Chicago, IL, USA (4)<br /> Dallas, TX, USA (4)<br />Des Moines,IA, USA (3)<br />Detroit, MI, USA<br />Englewood, CO, USA (2)<br />Honolulu, HI, USA<br />Houston, TX, USA (3)<br />Jacksonville, FL, USA (2)<br />Las Vegas, NV, USA (3)<br />Los Angeles, CA, USA (2)<br />Manassas, VA, USA (3)<br />Memphis, TN, USA<br /> Miami, FL, USA (4)<br />Minneapolis, MN, USA (2)<br />Needham Heights, MA, USA (2)<br /> Nashville, TN, USA<br />Newark, NJ, USA<br />New York, NY, USA (2)<br />Philadelphia, PA, USA<br />Phoenix, AZ, USA<br />Plano, TX, USA<br />Portland, OR, USA<br />Quincy, WA, USA (3)<br />San Antonio, TX, USA (4)<br />San Jose, CA, USA (4)<br />Salt Lake City, UT, USA (3)<br />Seattle, WA, USA (2)<br />Secaucus, NJ, USA (2)<br />Southfield, MI, USA<br />Tempe, AZ, USA<br /> |
+| North America | Etobicoke, Canada (2)<br />Montreal, Canada<br />Vancouver, Canada (2)<br />Querétaro, Mexico (2)<br />Atlanta, GA, USA (3)<br />Boydton, VA, USA (2)<br />Chaska, MN, USA (2)<br /> Cheyenne, WY, USA (2)<br />Chicago, IL, USA (4)<br /> Dallas, TX, USA (4)<br />Des Moines, IA, USA (3)<br />Detroit, MI, USA<br />Englewood, CO, USA (2)<br />Honolulu, HI, USA<br />Houston, TX, USA (3)<br />Jacksonville, FL, USA (2)<br />Las Vegas, NV, USA (3)<br />Los Angeles, CA, USA (2)<br />Manassas, VA, USA (3)<br />Memphis, TN, USA<br /> Miami, FL, USA (4)<br />Minneapolis, MN, USA (2)<br />Needham Heights, MA, USA (2)<br /> Nashville, TN, USA<br />Newark, NJ, USA<br />New York, NY, USA (2)<br />Philadelphia, PA, USA<br />Phoenix, AZ, USA<br />Plano, TX, USA<br />Portland, OR, USA<br />Quincy, WA, USA (3)<br />San Antonio, TX, USA (4)<br />San Jose, CA, USA (4)<br />Salt Lake City, UT, USA (3)<br />Seattle, WA, USA (2)<br />Secaucus, NJ, USA (2)<br />Southfield, MI, USA<br />Tempe, AZ, USA<br /> |
 | South America | Buenos Aires, Argentina<br />Campinas, Brazil (2)<br />Rio de Janeiro, Brazil (3)<br />Sao Paulo, Brazil (2)<br />Bogota, Colombia |
 | Europe | Zaventem, Belgium (2)<br />Sofia, Bulgaria (2)<br />Prague, Czech Republic<br />Ballerup, Denmark<br /> Vantaa, Finland<br />Les Ulis, France (3)<br />Paris, France<br />Saint Denis, France (2)<br />Berlin, Germany<br />Duesseldorf, Germany<br />Frankfurt, Germany (2)<br />Munich, Germany<br />Russelsheim, Germany (2)<br />Athens, Greece<br />Budapest, Hungary<br />Dublin, Ireland (2)<br />Milan, Italy<br />Rome, Italy (2)<br />Amsterdam, Netherlands<br />Oslo, Norway<br />Stavanger, Norway<br />Warsaw, Poland<br />Lisbon, Portugal<br />Bucharest, Romania<br />Barcelona, Spain<br />Madrid, Spain<br />Bromma, Sweden (2)<br />Zurich, Switzerland (2)<br />London, United Kingdom (5)<br />Manchester, United Kingdom |
 | Africa | Cairo, Egypt (2)<br />Nairobi, Kenya<br />Rabat, Morocco<br />Lagos, Nigeria<br />Cape Town, South Africa<br />Isando, South Africa (3) |