The service manager we have implemented for the automatic provisioning of Microsoft ESD services is been based on Microsoft CIS API (Channel Inclusion Services (CIS) Electronic Software Distribution (ESD)). Microsoft has exposed this API for creating perpetual licenses to their partner's end customers. |
Each ESD reseller that is using interworks.cloud Platform for offering MS ESD services, must generate his own authentication credentials (Channel ID, Client ID, Certificate Thumbprint) for activating the automatic provisioning of MS ESD services via interworks.cloud Platform.
Prerequisites Prior to Microsoft ESD Integration Activation A unique SSL certificate is required prior to activating the Microsoft ESD Integration for each customer having one or more currencies. The following three actions are necessary:
Example #1: A customer in the EU can send us a wildcard certificate (*.mydomain.com), inform us of the hostname "esd.mydomain.com" and declare the CNAME record for "esd.mydomain.com" which directs to the "cloud-platform-sites-eu.trafficmanager.net". Example #2: A customer in the US can send us a wildcard certificate (esd.mydomain.net), inform us of the host name "esd.mydomain.net" and declare the CNAME record for "esd.mydomain.net" which directs to the "cloud-platform-sites-us.trafficmanager.net". |
For activating the automatic provisioning of MS ESD services, you should do the following:
Certificate Thumbprint: Is unique per Distributor/Country/Language of charge
Language: Defines the products that will be created at the Get Services Definition action.
ESD Distributors that are eligible to resell in multiple countries/regions If you can resell ESD services in different countries/Regions you have to own different client IDs for each country. |