Marketing Cloud supports identity providers that utilize the SAML 2.0 specification, such as Salesforce Identity, Shibboleth, PingFederate, and Active Directory Federation Services (ADFS). The configuration for the identity provider must trust the Marketing Cloud product as a service provider, sometimes called a relying party. Azure Active Directory is a supported Identity Provider. The following information is designed to supplement documentation and guidance provided by Azure Active Directory, your IDP. Please consult with your IDP further if you run into any issues with the initial configuration.
Wait a few seconds while the app is added to your tenant. Within Azure Active Directory, a new 3rd Party Enterprise Application would be created to utilize SSO with the Marketing Cloud.
This file will process it may take a few seconds, and once complete, it will display the basic SAML configuration.
Once completed, then select Save. Then Download the Base64 signing cert. This is found under the Single Sign-On page under "Point 3" and was downloaded based on the above steps (Certificate (Base64) > Download).
Our Help Documentation on SSO can be found here. Everything needed is outlined on our help docs, but the below should hopefully supplement your configuration when specific to Azure.
Marketing Cloud SSO is enabled under Setup by a user that is a Marketing Cloud Administrator. Access the setup tab and then create a key under key management.
Once the Key is created, and Azure Active Directory is properly configured along with your users, you can now enable this for a test user in the Marketing Cloud.
SP Initiated example: https://mcYYYYYYYYYYYYYYYYYYYYYYYYY.login.exacttarget.com/sso/YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY IDP Initiated example: https://myapps.microsoft.com/signin/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX?tenantId=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Note:
Azure defaults the Enterprise SSO Saml config to SHA-254. You may need to update to SHA-1 in Azure as well as allow SHA-1 verification.
000381262

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.