Skip to content

Commit c6e8daf

Browse files
committed
Feedback changes
1 parent ad6cdd6 commit c6e8daf

8 files changed

+3
-87
lines changed

docs/azure/sdk/authentication/local-development-broker.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,6 @@ Brokered authentication offers the following benefits:
1919
- **System integration:** Applications that use the broker plug-and-play with the built-in account picker, allowing the user to quickly pick an existing account instead of reentering the same credentials over and over.
2020
- **Token Protection:** Ensures that the refresh tokens are device bound and enables apps to acquire device bound access tokens. See [Token Protection](/azure/active-directory/conditional-access/concept-token-protection).
2121

22-
:::image type="content" source="../media/mermaidjs/local-broker-authentication.svg" alt-text="A diagram showing how a local .NET app uses brokered credentials to connect to Azure resources.":::
23-
2422
:::zone target="docs" pivot="os-windows"
2523

2624
Windows provides an authentication broker called [Web Account Manager (WAM)](/entra/msal/dotnet/acquiring-tokens/desktop-mobile/wam). WAM enables identity providers such as Microsoft Entra ID to natively plug into the OS and provide secure login services to apps. Brokered authentication enables the app for all operations allowed by the interactive login credentials.

docs/azure/sdk/authentication/local-development-dev-accounts.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,6 @@ During local development, applications need to authenticate to Azure to access v
1919
- How to sign-in to supported local development tools
2020
- How to authenticate using a developer account from your app code
2121

22-
:::image type="content" source="../media/mermaidjs/local-developer-authentication.svg" alt-text="A diagram showing an app running in local development using a developer tool identity to connect to Azure resources.":::
23-
2422
For an app to authenticate to Azure during local development using the developer's Azure credentials, the developer must be signed-in to Azure from one of the following developer tools:
2523

2624
- Azure CLI

docs/azure/sdk/media/mermaidjs/authentication-environments.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,7 @@ flowchart LR
2020
%% Local Development Machine Branch
2121
Q1 --> LocalDev[Development machine]
2222
LocalDev --> AppSP["**Service principal**"]
23-
LocalDev --> DevAccount["**Developer account**"]
24-
LocalDev --> Broker["**Broker**"]
23+
LocalDev --> UserPrincipal["**User principal**"]
2524
2625
%% Azure Branch
2726
Q1 --> AzureApp[Azure]
@@ -42,6 +41,6 @@ flowchart LR
4241
4342
class NetApp startNode
4443
class Q1 questionBox
45-
class AppSP,DevAccount,Broker,ManagedId,ServicePrincipal authMethod
44+
class AppSP,UserPrincipal,ManagedId,ServicePrincipal authMethod
4645
class LocalDev,AzureApp,OnPremApp envNode
4746
```

docs/azure/sdk/media/mermaidjs/authentication-environments.svg

Lines changed: 1 addition & 1 deletion
Loading

docs/azure/sdk/media/mermaidjs/local-broker-authentication.md

Lines changed: 0 additions & 28 deletions
This file was deleted.

docs/azure/sdk/media/mermaidjs/local-broker-authentication.svg

Lines changed: 0 additions & 1 deletion
This file was deleted.

docs/azure/sdk/media/mermaidjs/local-developer-authentication.md

Lines changed: 0 additions & 49 deletions
This file was deleted.

docs/azure/sdk/media/mermaidjs/local-developer-authentication.svg

Lines changed: 0 additions & 1 deletion
This file was deleted.

0 commit comments

Comments
 (0)