Updated configuration credentials explanation - #2043
Conversation
|
MennoK999 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
1 similar comment
|
MennoK999 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
Bot
added
Change sent to author
entra-id/svc
saas-apps/subsvc
labels
|
Learn Build status updates of commit 90268d6: ✅ Validation status: passed
For more details, please refer to the build report. |
|
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.
Pull request overview
This PR updates the Zenya provisioning tutorial to clarify how to populate the Admin Credentials fields during SCIM configuration in Microsoft Entra ID.
Changes:
- Rewords the Admin Credentials step to reference the Tenant URL and Secret Token inputs and how to derive them from Zenya values.
- Normalizes formatting/indentation in the “Related content” section.
|  | ||
|
|
||
| 1. In the **Admin Credentials** section, input the **SCIM 2.0 base URL and Permanent Token** values retrieved earlier in the **Tenant URL** and add /scim/ to it. Also add the **Secret Token**. You can generate a secret token in Zenya by using the **permanent token** button. Select **Test Connection** to ensure Microsoft Entra ID can connect to Zenya. If the connection fails, ensure your Zenya account has Admin permissions and try again. | ||
| 1. In the **Admin Credentials** section, fill in the **Tenant URL** and **Secret Token**. Use the **Service Adress** and **permanent token** that you retrieved earlier. Add /scim/ to the **Tenant URL** and test the connection. |
No description provided.