Azure SAML Configuration Supporting Documentation

• Azure Supporting Documentation
• If you already have SAML configured for Azure...

Requirement: In order to connect using Azure for SAML and Office 365, the client needs an “Azure Active Directory Premium P1” license. This is required because the user will need to create an Enterprise App for SiteStacker and will need to use this claim with all the namespaces removed.

1. Configure SAML Setting in Azure

2. Pass us the federation metadata XML

3. Confirm all works as expected

 You use the below example attributes to configure attributes

• No attribute should be namespaced
• Attributes are also case-sensitive

4. Once you have set up your attributes, you will need to add multiple identifiers under “Basic SAML Configuration.”

5. Set the following Identifier (Entity ID):

   1. {https://domain.org}/simplesaml/module.php/saml/sp/metadata.php/default-sp

   2. {https://domain2.org}/simplesaml/module.php/saml/sp/metadata.php/default-sp

   3. {https://domain3.org}/simplesaml/module.php/saml/sp/metadata.php/default-sp

      1. Replace each {https://domain.org} with your domain(s)

      2. The first domain on the list should be your primary domain

6. Set the following Reply URL (Assertion Consumer Service URL):

   1. {https://domain.org}/simplesaml/module.php/saml/sp/saml2-acs.php/default-sp

      1. Replace {https://domain.org} with your primary domain

7. Set the following Relay State:

   1. {https://domain.org}g/p/Users/Saml/login

      1. Replace {https://domain.org} with your primary domain

8. Once Azure has been set up, the client will provide us with the XML file so DevOps can add Azure as a SAML option to their Site Stacker Installation.