Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback on documentation - "Authorize to Microsoft Graph" is confusing and seems out of place #303

Closed
jimbarrett33 opened this issue Apr 10, 2020 — with docs.microsoft.com · 3 comments · Fixed by #347
Assignees

Comments

Copy link

jimbarrett33 commented Apr 10, 2020

Just trying to help with the docs...

The section title is "Build an Azure AD connected add-in" and goes on to describe the 3-states of your add-in. Got that. Then the section ends with "to authenticate with Azure AD, see "Authorize to Microsoft Graph" which goes to a page titled "Authorize to Microsoft Graph without SSO"??? Not clear why the add-in cares about Microsoft Graph. I believe it's to allow the user to login to AAD to get user information from a tenant but that's not really clear.

Maybe a sentence or two as to why you're doing this and why the link to "Authorize to Microsoft Graph".


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@mscharlock
Copy link

@Lauragra can you weigh in on this? Thanks!

@Lauragra
Copy link
Collaborator

Lauragra commented Feb 3, 2021

@Rick-Kirkham , I think you own add-in authentication? Can you take a look please?

@Rick-Kirkham
Copy link
Contributor

Rick-Kirkham commented Feb 3, 2021

@jimbarrett33 I've replaced that link with two links that more appropriate. It should be republished in the next few days. The new links are the same ones that are lower down in the articl in the FAQ section in the answer to the question "How does my app authenticate a user with Azure AD?"

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

Successfully merging a pull request may close this issue.

4 participants