PREREQUISITES
-
A trust is established between SnapComms and the Microsoft Azure Active Directory
-
An Active Directory static group containing the users needing access to the Content Manager is created in Azure AD.
ESTABLISHING A TRUST
In the Content Manager, navigate to Management >> Integrations and click the Microsoft Account Integration button. Then, click on the Set up Microsoft sign in button.
If you have Domain Administrator access to your Microsoft Azure Active Directory, click on Complete authorization yourself. You will be taken to Microsoft Online (https://login.microsoftonline.com/common/oauth2/authorize) where you will complete the authorization process.
Otherwise, click on the Send sign up link button. In the pop up screen, enter the email address of the person that has Domain Administration access to your Microsoft Azure Active Directory. Entering a message is optional and will appear below the auto-generated message to be sent. Click the Send button.
An email will be sent to your Domain Administrator. Clicking the Authorize SnapComms button from the email received will take the Domain Administrator to Microsoft Online, where they will complete the authorization process.
CREATING AN ACTIVE DIRECTORY GROUP FOR CONTENT MANAGER ACCESS
Control over which users are able to access the SnapComms Content Manager is determined by a Microsoft Azure Active Directory Group. You can either create a new group or use an existing one. Obtain the Object ID for the group specified within Microsoft Azure Active Directory.
In the Content Manager, navigate to Management >> Integrations, then click on the Microsoft Account Integration button. Enter the Object ID into the Administrator Group ID field and click Save.
USING MICROSOFT ACCOUNT TO LOGIN TO THE CONTENT MANAGER
From the SnapComms login page click Log in with a Microsoft account.
If you are logged into your Microsoft Account, you will not be prompted to enter a username or password. Otherwise, enter your Microsoft credentials when prompted and click Login.
Comments
0 commentsArticle is closed for comments.