Azure AD Configuration
There is work that needs to be done on both sides and typically two different engineers will be working the issue, one on Azure and one in Connect. Step one is for the Azure engineer to setup a new application using the login link that agents would normally use to login to the Connect instance. You can find this on the Amazon Connect home page inside the AWS Management console. The Azure engineer will then provide a Metadata.XML file back to the AWS Engineer.
Step 2 AWS IAM Provider Configuration
Step 3 AWS IAM Role Configuration (
- Log in to AWS and open the IAM
- Click on Identity providers and then Create Provider.
- Choose the Provider Type as SAML.
- Enter Provider Name, such as “Azure AD”
- Upload a Federation Metadata XML (downloaded from previous step).
- Click Create Provider
More Information Here: https://docs.aws.amazon.com/connect/latest/adminguide/configure-saml.html )
- From the IAM/roles console Create a New Role
- Select SAML 2.0 Federation trusted entity type
- Select the Azure AD SAML provider from previous step
- Select Allow Programmatic and AWS Management Console access. The rest will auto-fill.
- On the Attach Permissions Policies Page create a policy like this:
- After policy is created, go back to Create Role tab, reload the policy list, and select your new policy.
- Set a role name and description, then click Create Role
- Open the new role and copy the Role ARN into notepad. Switch to the trust relationships tab and copy the Provider ARN into notepad.
Step 4 Create User for Azure to pull Roles for Users
1 - Create Policy "List Roles"
2 - Create User with programmatic access and attach the policy with the Access and Secret Keys
3 - Send me the Provider ARN and Role ARN back to the Azure engineer along with the User and Access Keys where the balance of the configuration is completed
The Azure engineer will then complete the Provisioning section setting the mode to Auto