Skip to Content

Hello,

We are seeing more and more installations where Cloud for Customer should be configured to use Microsoft Azure as SSO Identity Provider. In the past, we have seen some trouble regarding the NameID format. We worked on a solution and now Microsoft has added C4C as a preset to their Azure Gallery.

Microsoft has published a tutorial about how to configure C4C with Azure using their preset:

https://azure.microsoft.com/en-us/documentation/articles/active-directory-saas-sap-customer-cloud-tutorial

Best Regards,
Stefan

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. SVEN FEURER

    Hi Stefan,

    Thanks for sharing. Good to know. Here’s by the way a guide how we realized SSO via SAP’s HANA Cloud Identity Service (similar procedure via SAML): http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/409beece-b3d0-3210-079e-ce75f0780d0d?QuickLink=index&overridelayout=true&60155311953235.

    Regards,
    Sven

    (2) 
  2. Roberto Wahl

    Hi Stefan,

     

    are there any experience with this SSO Integration?

    We have tried to follow the instructions as close as possible. using the SSO URL redirects the browser to the Azure login page but after logging in we get an error: “AADSTS70001: application with identifier https://myxxxxxx-sso.crm.ondemand.com was not found in the directory xxxx”

    Do you have any recommendations for us?

     

    BR

    Roberto

     

    (0) 
  3. Richard Smart

    Hi Roberto,

    This was caused by a bug in Azure which Microsoft have now fixed. Its working fine now for me.

    One other thing we had to do was ensure the C4C user id had to match the Azure credentials (mail address) without the domain.

    e.g if the user logs into Azure with my.mail@domain.co.uk the C4C user id has to be my.mail

    Thanks

    Richard

     

     

    (0) 

Leave a Reply