Tutorial: Azure Active Directory single sign-on (SSO) integration with AWS Single Sign-on
In this tutorial, you'll learn how to integrate AWS Single Sign-on with Azure Active Directory (Azure AD). When you integrate AWS Single Sign-on with Azure AD, you can:
- Control in Azure AD who has access to AWS Single Sign-on.
- Enable your users to be automatically signed-in to AWS Single Sign-on with their Azure AD accounts.
- Manage your accounts in one central location - the Azure portal.
To get started, you need the following items:
- An Azure AD subscription. If you don't have a subscription, you can get a free account.
- AWS Single Sign-on single sign-on (SSO) enabled subscription.
In this tutorial, you configure and test Azure AD SSO in a test environment.
AWS Single Sign-on supports SP and IDP initiated SSO.
AWS Single Sign-on supports Automated user provisioning.
Adding AWS Single Sign-on from the gallery
To configure the integration of AWS Single Sign-on into Azure AD, you need to add AWS Single Sign-on from the gallery to your list of managed SaaS apps.
- Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
- On the left navigation pane, select the Azure Active Directory service.
- Navigate to Enterprise Applications and then select All Applications.
- To add new application, select New application.
- In the Add from the gallery section, type AWS Single Sign-on in the search box.
- Select AWS Single Sign-on from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
Configure and test Azure AD SSO for AWS Single Sign-on
Configure and test Azure AD SSO with AWS Single Sign-on using a test user called B.Simon. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in AWS Single Sign-on.
To configure and test Azure AD SSO with AWS Single Sign-on, perform the following steps:
- Configure Azure AD SSO - to enable your users to use this feature.
- Configure AWS Single Sign-on SSO - to configure the single sign-on settings on application side.
- Create AWS Single Sign-on test user - to have a counterpart of B.Simon in AWS Single Sign-on that is linked to the Azure AD representation of user.
- Test SSO - to verify whether the configuration works.
Configure Azure AD SSO
Follow these steps to enable Azure AD SSO in the Azure portal.
In the Azure portal, on the AWS Single Sign-on application integration page, find the Manage section and select single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set up single sign-on with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.
If you have Service Provider metadata file, on the Basic SAML Configuration section, perform the following steps:
a. Click Upload metadata file.
b. Click on folder logo to select the metadata file which you have downloaded from the Configure AWS Single Sign-on SSO section (point 8) and click Add.
c. Once the metadata file is successfully uploaded, the Identifier and Reply URL values get auto populated in Basic SAML Configuration section:
If the Identifier and Reply URL values are not getting auto populated, then fill in the values manually according to your requirement.
If you don't have Service Provider metadata file, perform the following steps on the Basic SAML Configuration section, if you wish to configure the application in IDP initiated mode, enter the values for the following fields:
a. In the Identifier text box, type a URL using the following pattern:
b. In the Reply URL text box, type a URL using the following pattern:
Click Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:
In the Sign-on URL text box, type a URL using the following pattern:
These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact AWS Single Sign-on Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
AWS Single Sign-on application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
If ABAC is enabled in AWS SSO, the additional attributes may be passed as session tags directly into AWS accounts.
On the Set up single sign-on with SAML page, in the SAML Signing Certificate section, find Certificate(Base64) and select Download to download the certificate and save it on your computer.
On the Set up AWS Single Sign-on section, copy the appropriate URL(s) based on your requirement.
Create an Azure AD test user
In this section, you'll create a test user in the Azure portal called B.Simon.
- From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
- Select New user at the top of the screen.
- In the User properties, follow these steps:
- In the Name field, enter
- In the User name field, enter the firstname.lastname@example.org. For example,
- Select the Show password check box, and then write down the value that's displayed in the Password box.
- Click Create.
- In the Name field, enter
Assign the Azure AD test user
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to AWS Single Sign-on.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select AWS Single Sign-on.
- In the app's overview page, find the Manage section and select Users and groups.
- Select Add user, then select Users and groups in the Add Assignment dialog.
- In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
- If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
- In the Add Assignment dialog, click the Assign button.
Configure AWS Single Sign-on SSO
To automate the configuration within AWS Single Sign-on, you need to install My Apps Secure Sign-in browser extension by clicking Install the extension.
After adding extension to the browser, click on Set up AWS Single Sign-on will direct you to the AWS Single Sign-on application. From there, provide the admin credentials to sign into AWS Single Sign-on. The browser extension will automatically configure the application for you and automate steps 3-10.
If you want to setup AWS Single Sign-on manually, in a different web browser window, sign in to your AWS Single Sign-on company site as an administrator.
Go to the Services -> Security, Identity, & Compliance -> AWS Single Sign-On.
In the left navigation pane, choose Settings.
On the Settings page, find Identity source and click on Change.
On the Change identity source, choose External identity provider.
Perform the below steps in the Configure external identity provider section:
a. In the Service provider metadata section, find AWS SSO SAML metadata and select Download metadata file to download the metadata file and save it on your computer and use this metadata file to upload on Azure portal.
b. Copy AWS SSO Sign-in URL value, paste this value into the Sign on URL text box in the Basic SAML Configuration section in the Azure portal.
c. In the Identity provider metadata section, choose Browse to upload the metadata file which you have downloaded from the Azure portal.
d. Choose Next: Review.
In the text box, type ACCEPT to change the identity source.
Click Change identity source.
Create AWS Single Sign-on test user
Open the AWS SSO console.
In the left navigation pane, choose Users.
On the Users page, choose Add user.
On the Add user page, follow these steps:
a. In the Username field, enter B.Simon.
b. In the Email address field, enter the
email@example.com. For example,
c. In the Confirm email address field, re-enter the email address from the previous step.
d. In the First name field, enter
e. In the Last name field, enter
f. In the Display name field, enter
g. Choose Next: Groups.
Make sure the username entered in AWS SSO matches the user’s Azure AD sign-in name. This will you help avoid any authentication problems.
Choose Add user.
Next, you will assign the user to your AWS account. To do so, in the left navigation pane of the AWS SSO console, choose AWS accounts.
On the AWS Accounts page, select the AWS organization tab, check the box next to the AWS account you want to assign to the user. Then choose Assign users.
On the Assign Users page, find and check the box next to the user B.Simon. Then choose Next: Permission sets.
Under the select permission sets section, check the box next to the permission set you want to assign to the user B.Simon. If you don’t have an existing permission set, choose Create new permission set.
Permission sets define the level of access that users and groups have to an AWS account. To learn more about permission sets, see the AWS SSO Permission Sets page.
AWS Single Sign-on also supports automatic user provisioning, you can find more details here on how to configure automatic user provisioning.
In this section, you test your Azure AD single sign-on configuration with following options.
Click on Test this application in Azure portal. This will redirect to AWS Single Sign-on Sign on URL where you can initiate the login flow.
Go to AWS Single Sign-on Sign-on URL directly and initiate the login flow from there.
- Click on Test this application in Azure portal and you should be automatically signed in to the AWS Single Sign-on for which you set up the SSO
You can also use Microsoft My Apps to test the application in any mode. When you click the AWS Single Sign-on tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the AWS Single Sign-on for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.
Once you configure AWS Single Sign-on you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Cloud App Security.