Connecting Mosaic with Microsoft Azure

Initial Setup with Microsoft Azure SAML

1. On the Welcome to Azure! page, find the Enterprise applications option.

2. Click on the Enterprise applications option and click on New application.

3. Click on the Create your own application button.

4. Input a name that is easily identifiable and select Integrate any other application you don't find in the gallery (Non-gallery).

5. Once the app has been created by Azure, navigate to the Single sign-on menu and select SAML.

6. Go to Mosaic settings → Security → SAML 2.0 Single Sign On

🚧

Please Note:

Only admins are able to access the “Security“ tab on Mosaic settings.

7. On Mosaic’s SAML 2.0 Single Sign On menu, fill in:

• Domain:
  • Domain associated with Microsoft Azure.
    • For example, [email protected] has a domain of thisisdomain.com.

🚧

Please Note:

The email associated with the admin (who is setting up the SAML) must have the same domain as the one being inputted.

• For example, if the admin uses an email [email protected], the only domain the admin could input is thisisdomain.com.

• SSO URL:

  • Copy the Login URL under Set up [name of the application] App from Step #4 of the Azure Single sign-on menu.

• Certificate:

  • Download Certificate (Base64) under SAML Signing Certificate in Step #3 of the Azure Single sign-on menu.
  • Open downloaded certificate with a text editor of choice.
  • Copy the full content of the certificate.

8. Copy and paste ACS URL and Entity ID from Mosaic’s SAML 2.0 Single Sign On menu to Microsoft Azure’s Basic SAML Configuration section; all other fields can remain untouched.

9. Add a group to the SAML app through the Users and groups menu.

• Create a group on Azure
  • Search for Groups

• Create a new Group

• Ensure the Group Type is Security , then fill out the Group Name

• Assign Members you want to be authorized for the Mosaic Team

  • Note down the Object ID of the new Group you just created. This will be entered into Mosaic in a new field for Security Group ID
• 

  Then go back to the SAML app and add the Group through the Users and Groups Menu.

• You no longer need to add Users, instead you should add a Group , and the Users to the Group you added in the SAML app.

10. Next, click on Attributes & Claims and then Add new claim.

    
    
    • Add the following additional attributes:
      a. email

    Mapping Source Attributes

    🚧

    Configuring Source Attribute Mapping for Email Aliases

    To ensure seamless integration with Single Sign-On (SSO) systems, it's crucial to correctly configure the mapping of source attributes. This configuration allows the use of an email alias instead of the actual mailbox address for SSO authentication.

    For instance, consider you're employing [email protected] as the alias and [email protected] as the primary mailbox address. In this scenario, the configuration on the Azure platform should map the source attribute to the alias ([email protected]), not to the mailbox ([email protected]).

    For a full list of user profile attributes in Azure Active Directory B2C, refer to the Microsoft documentation here.

    This setup is vital for aligning with Azure's user profile configuration requirements for aliases and mailbox addresses.

    

    b. first_name

    

    c. last_name

• Go back to Attributes & Claims and also Add a group claim.
• Select Groups assigned to the application and enter a Custom Name like security_group.

• Hit save and then SAML will be all set.

🚧

Setting up Multiple Teams with SAML:

• To set up multiple teams with SAML simply create another group and add users to that group. (Users can only be in 1 group!)
• When setting up SAML on the new Mosaic team. Skip the step to copy the ACS URL and the Entity ID.
• Then copy the new Object ID of the new Group and paste it into the Security Group ID box when setting up SAML on the new Mosaic team.

11. Next, go back to Mosaic and click Done.

• Upon successful activation, SAML 2.0 Single Sign On will have the following options.

12. Next time a user with an email address belonging to the specified domain logs into Mosaic, they will be redirected to authenticate with Microsoft Azure the moment they click Next after inputting their email.

🚧

Ensure Azure User Activation Before Creating Mosaic Account

It is recommended to ensure that a new Azure user is fully active (or wait a few days) before creating a new user on Mosaic. If the Azure account is not fully active, the Welcome Email may hard bounce with the 550 5.4.1 error code (The recipient's address doesn't exist). Unfortunately, AWS, which sends the invitation email, places the email address on a blacklist if the email hard bounces, and no further emails will be sent out.