Publisher verification status missing from Azure SSO Consent Dialog

SCT-Akouodev
26
Reputation points
We're developing an MS Teams Tab application in a multi-tenant setup.
We're using Azure SSO for authentication as documented here, and also the authorization code flow for requesting additional Graph Permissions.
As promised in the Publisher Verification documentation, the app logo and badge are being displayed in the Graph consent dialog.
But the same verification status is missing from the SSO consent dialog.
This is an issue because we are unable to publish the app to the MS Teams App Store without the proper 'verified publisher' experience.
{count} votes
Hi @Prasad-MSFT ,
Thanks for responding.
We have followed the exact steps for adding SSO from here and for Publisher Verification from here.
Note that for Publisher Verification we have verified a custom domain name.
@SCT-Akouodev - Is the same AAD app registered in Azure Portal being used for both of these flows?
Yes, the app ID is the same in the following places -
Please reach out to the Identity org since they are the ones that render these consent dialogs. You can find guidance for reaching them here:
https://identitydocs.azurewebsites.net/static/v2/get_help.html
Thanks!
I am unable to access the page at https://identitydocs.azurewebsites.net/static/v2/get_help.html.
Is this an internal document? Can you please point me to a public page/forum to raise this request?
Thanks.
We have updated the tags so that Identity team can help with this question.
We are facing exactly the same issue and the app submission team blocked our app for this very reason.
Hi @Prasad-MSFT ,
We are facing the same problem: the verified badge is not shown in the initial SSO consent, but is shown in all other consent contexts. Has a root cause or solution been identified for this problem? We have tried just about everything we can think of without success.
Please reach out to the Identity org since they are the ones that render these consent dialogs. You can find guidance for reaching them here:
https://identitydocs.azurewebsites.net/static/v2/get_help.html
@Prasad-MSFT I receive a similar error as @SCT-Akouodev reported above when attempting to access the link you provided. Is there another way I can contact the identity org?
We have updated the tags so that Identity team can help with this question.
We have exactly the same issue with our Teams App. The project was created using the Microsoft Teams Toolkit and the contained SSO webapp.
Is there any update on this issue?
Sign in to comment
1 answer
Sort by: Most helpful
We found a workaround: instead of relying on SSO to request consent, catch the consent error and redirect the user to the authorization page requesting the same scopes as SSO. For whatever reason, manually requesting the scopes instead of relying on SSO gets the badge to display in the consent dialog.
Sign in to comment
Activity