Azure-docs: Missing Reply URL

Created on 24 Jan 2020  Â·  11Comments  Â·  Source: MicrosoftDocs/azure-docs

Zoom's document states you must have a Reply Url Set: https://support.zoom.us/hc/en-us/articles/115005887566-Configuring-Zoom-with-Azure#h_04f20f53-96b6-4877-9b14-b1a862fe34c8

For Identifier (Entity ID), enter your vanity URL without https://.
Eg. yourvanityurl.zoom.us

For Reply URL, enter https://*.zoom.us/saml/SSO

For Sign on URL, enter https:// followed by your Vanity URL.
Eg. https://yourvanityurl.zoom.us


Document Details

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

Pri2 active-directorsvc assigned-to-author doc-bug saas-app-tutoriasubsvc triaged

Most helpful comment

Wildcards are not supported:

Reply URL (Assertion Consumer Service URL)
The default reply URL will be the destination in the SAML response for IDP-initiated SSO
https://*.zoom.us/saml/SSO
Wild cards * are not supported.

Seeing the same issue. I have a feeling the "no wild cards" thing is new because I'm pretty sure I've set it that way in the past. Not sure what to do for Zoom setup now as they want a wild card in the Reply URL field.

All 11 comments

Hello @afield1235 ,

Thank you for your feedback! We will review and provide an update as appropriate.

@chetansriv for tracking

Wildcards are not supported:

Reply URL (Assertion Consumer Service URL)
The default reply URL will be the destination in the SAML response for IDP-initiated SSO
https://*.zoom.us/saml/SSO
Wild cards * are not supported.

Wildcards are not supported:

Reply URL (Assertion Consumer Service URL)
The default reply URL will be the destination in the SAML response for IDP-initiated SSO
https://*.zoom.us/saml/SSO
Wild cards * are not supported.

Seeing the same issue. I have a feeling the "no wild cards" thing is new because I'm pretty sure I've set it that way in the past. Not sure what to do for Zoom setup now as they want a wild card in the Reply URL field.

I've also run into this. Commenting to track.

That setup works and is in production. Not sure what you mean by it's not supported. What should we be using then? There shouldn't be discrepancies between documentation. I don't think I've done ONE Azure AD SSO implementation was 100% accurate in terms of documentation. Very frustrating..

It looks like Zoom updated their documentation:
https://support.zoom.us/hc/en-us/articles/115005887566
Reply URL doesn't require a wild card anymore.

I believe my original point still stands, everyone got sidetracked with the discussion on wildcards. The Azure Documentation does not include any mention of Reply URLS, but mentions all other values, while the Zoom documentation states the need for a Reply URL.

Microsoft, please update your documentation to include this.

image

@chetansriv for tracking.

Please close this PR, we resolved the issue in another PR which is merged now _https://github.com/MicrosoftDocs/azure-docs-pr/pull/125329_

please-close

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Agazoth picture Agazoth  Â·  3Comments

spottedmahn picture spottedmahn  Â·  3Comments

AronT-TLV picture AronT-TLV  Â·  3Comments

Ponant picture Ponant  Â·  3Comments

bityob picture bityob  Â·  3Comments