azure-docs
azure-docs copied to clipboard
Request to add appropriate Microsoft Docs link for enabling SSO when it's disabled
A lot of users have reported the SSO disabled experience to be their default and scramble to guide their admins with information on what they are asking for. In some cases the Admins were aware what to configure. Could you please link to the appropriate Microsoft docs that addresses the 2nd pre-requisite around SSO if it's disabled? Thank you!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 6535ed3f-d135-2a94-7007-ec2214d298d6
- Version Independent ID: 39f5315c-bf32-ef83-d27e-bb7fb1b4b010
- Content: Create Elastic application - Azure partner solutions
- Content Source: articles/partner-solutions/elastic/create.md
- Service: partner-services
- Sub-service: elastic
- GitHub Login: @davidsmatlak
- Microsoft Alias: davidsmatlak
#assign:davidsmatlak
@hemantmalik Thanks for the feedback. The doc mentions that the SSO app is automatically enabled, so please clarify what you mean by the SSO disabled experience? Is there a specific Microsoft doc about SSO that you want included in the article?
Thanks @davidsmatlak for the quick response. A lot of users experience that they can't SSO to the service when they try to navigate from Azure Portal. They are presented with something similar to below screenshot. Most of those users have struggled to
- find out "who" they should reach out within their Azure ecosystem and (a problem hard to solve for us)
- "what" are they asking to be done - this is where I am hoping if there is a Microsoft documentation that provides directions about how the SSO can be enabled would help these users make the specific ask. Just an example but something like this that's applicable could be helpful: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sso-quick-start
@hemantmalik Thanks for the update. I'll follow up with the product team about your questions.
#reassign:flang-msft
Reassigned to @flang-msft who will follow up with the product team.
#reassign: rotata
I've re-assigned this hoping that @rotata can give you information on how to create a bug on this issue.
Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close