Skip to content

Commit ad6cdd6

Browse files
committed
image changes
1 parent 813aeb8 commit ad6cdd6

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

docs/azure/sdk/authentication/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -69,19 +69,19 @@ You can use your own Azure credentials to authenticate to Azure resources during
6969
> [!div class="nextstepaction"]
7070
> [Authenticate locally using developer credentials](local-development-dev-accounts.md)
7171
72-
#### Use a service principal
72+
#### Use a broker
7373

74-
A service principal is created in a Microsoft Entra tenant to represent an app and be used to authenticate to Azure resources. You can configure your app to use service principal credentials during local development. This method is more secure than using developer credentials and is closer to how your app will authenticate in production. However, it's still less ideal than using a managed identity due to the need for secrets.
74+
Brokered authentication collects user credentials using the system authentication broker to authenticate an app. A system authentication broker runs on a user's machine and manages the authentication handshakes and token maintenance for all connected accounts.
7575

7676
> [!div class="nextstepaction"]
77-
> [Authenticate locally using a service principal](local-development-service-principal.md)
77+
> [Authenticate locally using a broker](local-development-broker.md)
7878
79-
#### Use a broker
79+
#### Use a service principal
8080

81-
Brokered authentication collects user credentials using the system authentication broker to authenticate an app. A system authentication broker runs on a user's machine and manages the authentication handshakes and token maintenance for all connected accounts.
81+
A service principal is created in a Microsoft Entra tenant to represent an app and be used to authenticate to Azure resources. You can configure your app to use service principal credentials during local development. This method is more secure than using developer credentials and is closer to how your app will authenticate in production. However, it's still less ideal than using a managed identity due to the need for secrets.
8282

8383
> [!div class="nextstepaction"]
84-
> [Authenticate locally using a broker](local-development-broker.md)
84+
> [Authenticate locally using a service principal](local-development-service-principal.md)
8585
8686
## Authentication for apps hosted on-premises
8787

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ flowchart LR
1818
NetApp --> Q1
1919
2020
%% Local Development Machine Branch
21-
Q1 --> LocalDev[Development Machine]
21+
Q1 --> LocalDev[Development machine]
2222
LocalDev --> AppSP["**Service principal**"]
2323
LocalDev --> DevAccount["**Developer account**"]
2424
LocalDev --> Broker["**Broker**"]

0 commit comments

Comments
 (0)