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

Links to 'What Happened...' not working #19104

Closed
tx5westmt opened this issue Nov 17, 2018 — with docs.microsoft.com · 5 comments
Closed

Links to 'What Happened...' not working #19104

tx5westmt opened this issue Nov 17, 2018 — with docs.microsoft.com · 5 comments

Comments

Copy link
Contributor

Both links in intro to verify 'what happened' are redirecting to this page instead of the details on what changes when adding this as a connected services.


Document Details

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

@BryanTrach-MSFT
Copy link
Member

@tx5westmt Thanks for the feedback! We are currently investigating and will update you shortly.

@MohitGargMSFT
Copy link
Member

@tx5westmt Thanks for reporting! I have assigned the issue to the content author to investigate and update as appropriate.

@stevebelskie
Copy link
Contributor

Any update on this? It's not clear from the article what (if anything) the connected service does that simply using the AppAuth and KeyVault packages do not. I'm guessing when creating resource (and maybe when linking to an existing one) an access policy is being created for the account. But there is also a Nuget package being installed Microsoft.Exstensions.AzureKeyVault.HostingStartup and some environmental variables being set in launchsettings.json. I'd like to know what the effect is here.

@ghogen
Copy link
Contributor

ghogen commented Mar 21, 2019

It appears those topics were deleted. I restored the content and added them to the main topic. This change should show up within a day.

@ghogen
Copy link
Contributor

ghogen commented Mar 21, 2019

#please-close

ghost pushed a commit that referenced this issue Mar 21, 2019
Fixes issues #19104 and VS 2019 updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants