From c1d928ed020d8d334f22572f20e237865815b7bb Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Mon, 13 Oct 2025 14:57:13 -0400 Subject: [PATCH 1/5] Use includes from shared repo --- .../sdk/authentication/local-development-dev-accounts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/azure/sdk/authentication/local-development-dev-accounts.md b/docs/azure/sdk/authentication/local-development-dev-accounts.md index 4c32dcaae1c7f..f4b540640fd61 100644 --- a/docs/azure/sdk/authentication/local-development-dev-accounts.md +++ b/docs/azure/sdk/authentication/local-development-dev-accounts.md @@ -32,9 +32,9 @@ The Azure Identity library can detect that the developer is signed-in from one o This approach takes advantage of the developer's existing Azure accounts to streamline the authentication process. However, a developer's account likely has more permissions than required by the app, therefore exceeding the permissions the app runs with in production. As an alternative, you can [create application service principals to use during local development](./local-development-service-principal.md), which can be scoped to have only the access needed by the app. -[!INCLUDE [auth-create-entra-group](../includes/auth-create-entra-group.md)] +[!INCLUDE [auth-create-entra-group](~/../azure-dev-docs-pr/articles/includes/authentication/auth-create-entra-group.md)] -[!INCLUDE [auth-assign-group-roles](../includes/auth-assign-group-roles.md)] +[!INCLUDE [auth-assign-group-roles](~/../azure-dev-docs-pr/articles/includes/authentication/auth-assign-group-roles.md)] ## Sign-in to Azure using developer tooling @@ -94,4 +94,4 @@ Connect-AzAccount -UseDeviceAuthentication --- -[!INCLUDE [Implement DefaultAzureCredential](<../includes/implement-defaultazurecredential.md>)] +[!INCLUDE [Implement DefaultAzureCredential](~/../azure-dev-docs-pr/articles/includes/authentication/implement-defaultazurecredential.md)] From 62b11aaef309e5062cec46b901bfb8a1c78c6b60 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Mon, 13 Oct 2025 15:02:20 -0400 Subject: [PATCH 2/5] fix path --- .../sdk/authentication/local-development-dev-accounts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/azure/sdk/authentication/local-development-dev-accounts.md b/docs/azure/sdk/authentication/local-development-dev-accounts.md index f4b540640fd61..b035808df2609 100644 --- a/docs/azure/sdk/authentication/local-development-dev-accounts.md +++ b/docs/azure/sdk/authentication/local-development-dev-accounts.md @@ -32,9 +32,9 @@ The Azure Identity library can detect that the developer is signed-in from one o This approach takes advantage of the developer's existing Azure accounts to streamline the authentication process. However, a developer's account likely has more permissions than required by the app, therefore exceeding the permissions the app runs with in production. As an alternative, you can [create application service principals to use during local development](./local-development-service-principal.md), which can be scoped to have only the access needed by the app. -[!INCLUDE [auth-create-entra-group](~/../azure-dev-docs-pr/articles/includes/authentication/auth-create-entra-group.md)] +[!INCLUDE [auth-create-entra-group](~/../azure-dev-docs-pr/articles/includes/authentication/includes/auth-create-entra-group.md)] -[!INCLUDE [auth-assign-group-roles](~/../azure-dev-docs-pr/articles/includes/authentication/auth-assign-group-roles.md)] +[!INCLUDE [auth-assign-group-roles](~/../azure-dev-docs-pr/articles/includes/authentication/includes/auth-assign-group-roles.md)] ## Sign-in to Azure using developer tooling @@ -94,4 +94,4 @@ Connect-AzAccount -UseDeviceAuthentication --- -[!INCLUDE [Implement DefaultAzureCredential](~/../azure-dev-docs-pr/articles/includes/authentication/implement-defaultazurecredential.md)] +[!INCLUDE [Implement DefaultAzureCredential](~/../azure-dev-docs-pr/articles/includes/authentication/includes/implement-defaultazurecredential.md)] From e9e93e642c32b3422cd31fb5cb10318d8941d88b Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Mon, 13 Oct 2025 15:22:01 -0400 Subject: [PATCH 3/5] Fix path --- .../sdk/authentication/local-development-dev-accounts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/azure/sdk/authentication/local-development-dev-accounts.md b/docs/azure/sdk/authentication/local-development-dev-accounts.md index b035808df2609..3fb908b50c1c8 100644 --- a/docs/azure/sdk/authentication/local-development-dev-accounts.md +++ b/docs/azure/sdk/authentication/local-development-dev-accounts.md @@ -32,9 +32,9 @@ The Azure Identity library can detect that the developer is signed-in from one o This approach takes advantage of the developer's existing Azure accounts to streamline the authentication process. However, a developer's account likely has more permissions than required by the app, therefore exceeding the permissions the app runs with in production. As an alternative, you can [create application service principals to use during local development](./local-development-service-principal.md), which can be scoped to have only the access needed by the app. -[!INCLUDE [auth-create-entra-group](~/../azure-dev-docs-pr/articles/includes/authentication/includes/auth-create-entra-group.md)] +[!INCLUDE [auth-create-entra-group](~/azure-dev-docs-pr/articles/includes/authentication/includes/auth-create-entra-group.md)] -[!INCLUDE [auth-assign-group-roles](~/../azure-dev-docs-pr/articles/includes/authentication/includes/auth-assign-group-roles.md)] +[!INCLUDE [auth-assign-group-roles](~/azure-dev-docs-pr/articles/includes/authentication/includes/auth-assign-group-roles.md)] ## Sign-in to Azure using developer tooling @@ -94,4 +94,4 @@ Connect-AzAccount -UseDeviceAuthentication --- -[!INCLUDE [Implement DefaultAzureCredential](~/../azure-dev-docs-pr/articles/includes/authentication/includes/implement-defaultazurecredential.md)] +[!INCLUDE [Implement DefaultAzureCredential](~/azure-dev-docs-pr/articles/includes/authentication/includes/implement-defaultazurecredential.md)] From 2ca0a4c0db73b9240869d4dc5718043efa4161e3 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Mon, 13 Oct 2025 15:32:34 -0400 Subject: [PATCH 4/5] fix link --- docs/ai/quickstarts/includes/ai-templates-azure-openai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ai/quickstarts/includes/ai-templates-azure-openai.md b/docs/ai/quickstarts/includes/ai-templates-azure-openai.md index 8d7a4098d161e..756aa2dedbab9 100644 --- a/docs/ai/quickstarts/includes/ai-templates-azure-openai.md +++ b/docs/ai/quickstarts/includes/ai-templates-azure-openai.md @@ -87,7 +87,7 @@ The AI template uses Microsoft Entra ID for seamless, keyless authentication. It * In the Azure Portal, navigate to the overview page of your Azure OpenAI resource. * Select **Access control (IAM)** from the left navigation. - * [Add a role assignment](../../../azure/sdk/authentication/local-development-dev-accounts.md#assign-roles-to-the-group) for the `Azure AI Developer` role to your Azure account. + * [Add a role assignment](/dotnet/azure/sdk/authentication/local-development-dev-accounts#assign-roles-to-the-group) for the `Azure AI Developer` role to your Azure account. 1. [Sign-in to a local development tool](../../../azure/sdk/authentication/local-development-dev-accounts.md#sign-in-to-azure-using-developer-tooling) such as Visual Studio or the Azure CLI using the Azure account you assigned the `Azure AI Developer` role to. From b72e4d7939df934df33182dc8e068d23bbb51e36 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Mon, 13 Oct 2025 16:45:23 -0400 Subject: [PATCH 5/5] fix link --- docs/azure/sdk/authentication/local-development-dev-accounts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/azure/sdk/authentication/local-development-dev-accounts.md b/docs/azure/sdk/authentication/local-development-dev-accounts.md index 3fb908b50c1c8..5113e1a2a633a 100644 --- a/docs/azure/sdk/authentication/local-development-dev-accounts.md +++ b/docs/azure/sdk/authentication/local-development-dev-accounts.md @@ -94,4 +94,4 @@ Connect-AzAccount -UseDeviceAuthentication --- -[!INCLUDE [Implement DefaultAzureCredential](~/azure-dev-docs-pr/articles/includes/authentication/includes/implement-defaultazurecredential.md)] +[!INCLUDE [Implement DefaultAzureCredential](../includes/implement-defaultazurecredential.md)]