-
Notifications
You must be signed in to change notification settings - Fork 750
Update optimizely-tutorial.md #1480
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
Conversation
The existing instructions for SSO integration between Microsoft Entra and Optimizely were outdated. They referred to the SSO connection for the standalone Optimizely Experimentation platform. Nowadays, the access to the multiple Optimizely products is centralized in Opti ID. The SSO configuration needs to be set up via the Optimizely Admin Center. The Optimizely knowledge base article is kept up-to-date, and so it's recommended to refer to that article, and not have outdated documentations that confuse customers.
@microsoft-github-policy-service agree company="Optimizely" |
@optimizer-david : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit d3c315f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes accepted
#sign-off |
The existing instructions for SSO integration between Microsoft Entra and Optimizely were outdated. They referred to the SSO connection for the standalone Optimizely Experimentation platform.
Nowadays, the access to the multiple Optimizely products is centralized in Opti ID. The SSO configuration needs to be set up via the Optimizely Admin Center. The Optimizely knowledge base article is kept up-to-date, and so it's recommended to refer to that article, and not have outdated documentations that confuse customers.