Skip to content

Conversation

alexwolfmsft
Copy link
Contributor

@alexwolfmsft alexwolfmsft commented Aug 29, 2025

@alexwolfmsft alexwolfmsft marked this pull request as ready for review August 29, 2025 15:35
@alexwolfmsft
Copy link
Contributor Author

@scottaddie I went ahead and replaced the remaining legacy diagrams with standardized/editable mermaid diagrams - just let me know if you want any changes or if you'd prefer not to replace some of them.

alexwolfmsft and others added 2 commits September 2, 2025 15:53
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
Comment on lines +22 to +24
LocalDev --> AppSP["**Service principal**"]
LocalDev --> DevAccount["**Developer account**"]
LocalDev --> Broker["**Broker**"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we are mixing concepts here - Broker would be a developer account also. Should we use only Service principal and User principal? We could probably get rid of Broker.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea behind this diagram is the authentication approach or technique that the user would implement, so even though the underlying account is the same its acquired using a different approach.

%% npm i -g @mermaid-js/mermaid-cli@10.9.1
%% 2. Run command: mmdc -i local-broker-authentication.md -o ../../media/mermaidjs/local-broker-authentication.svg

flowchart LR
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are we trying to communicate with this diagram? I think we should either use a component diagram that illustrates how the broker interacts with the application or remove it.

VS --> DevAccount
VSC --> DevAccount
AZD --> DevAccount
AZCLI --> DevAccount
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CLI and perhaps others can authenticate service principles in addition to developer accounts. I'm not sure if this diagram adds any new information other than these tools can interact with developer credentials.

VSC --> DevAccount
AZD --> DevAccount
AZCLI --> DevAccount
AZPS --> DevAccount

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Broker is also part of the Dev credentials; it's another way to get access to the Developer account credentials

AS["Azure services"]

APP --> BK
BK --> AS

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be helpful to add another layer to this diagram to emphasize that the Broker is part of Windows (WAM), Intune in Linux and MacOS and that these OS component and tools are the one interacting with the .NET App to get the User's credentials.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants