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.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@tx5westmt Thanks for the feedback! We are currently investigating and will update you shortly.
@tx5westmt Thanks for reporting! I have assigned the issue to the content author to investigate and update as appropriate.
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.
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.
Most helpful comment
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.HostingStartupand some environmental variables being set inlaunchsettings.json. I'd like to know what the effect is here.