This issue happens because it is impossible to add self created certificate to the trusted list of Authorities in Azure as it is global thing.
But for developers environment, we should be able to use self signed certificates instead of purchasing real ones.
For certificates purchased from trusted vendors will not be an issue.
You just need to add a parameter AllowInvalidClientCertificates=true for every connection string which contains certificate
you will have something like:
<add name="xconnect.collection.certificate" connectionString="StoreName=My;StoreLocation=CurrentUser;FindType=FindByThumbprint;FindValue=AAAAAA34364908AB8A72CBED502FEDC9DDB5A2;AllowInvalidClientCertificates=true" />
You need to have it in 4 places :
In the interest of saving people time, when deploying the xP1 topology in Azure PaaS, you will need to update the connection strings for the following 5 roles:
- Content Delivery (cd)
- Content Management (cm)
- Processing (prc)
- Marketing Automation - Operations (ma-ops)
- Dedicated Delivery Service (exm-dds)