Getting Started with the Cloud Solution Provider APIs

If you're a Cloud Solution Provider (CSP) partner, you have many options for transacting your customers orders with Microsoft. In this post I'll walk through getting started with the CSP Application Programming Interfaces (APIs) and point you to some resources for learning more about them.

Most partners who undertake CSP API integration work do so because they have an existing customer portal where their customers purchase from them and they want to have direct integration between that portal and Microsoft. This would enable the partner to sell Microsoft commercial cloud services directly from their own portal through the CSP program. Here are some other options for selling through the CSP program.

• Code against CSP APIs - this is what I'll focus on below in the post
• Use Partner Center web site - You can use the Partner Center web site that Microsoft provides, but your customers cannot access that so you have to place the orders for them
• Panel Providers Prebuilt Portal - You can use a 'control panel' from an ISV who specializes in that and their software will access the CSP APIs on your behalf
• Use a Distributors Portal - If you are a reseller working with a 2 tier CSP distributor then you would normally use the portal that the distributor provides
• Hire Third Party Developer - The other way you can avoid coding against the APIs is to hire developers who can do it for you

To be successful with the Cloud Solution Provider CREST APIs you should already have the following pre-requisites:

• Must be already on-boarded as a Cloud Solution Provider partner with access to https://partnercenter.microsoft.com
• Have developers with experience using REST and JSON. All integration with the CSP APIs uses industry standards based REST and JSON message formats over HTTPS.
• Ideally developers should also have experience with Azure AD authentication and C#. It is not required to use C# since the APIs are available to any language which supports REST, however we provide the most comprehensive sample code in C# using Visual Studio 2015 and .NET Framework 4.5.

Make sure you know who your software developers are who will be working on the integration project. Perhaps it is you. That person should review the available training material for working with the CSP APIs. We have links to this at the end of this document and it includes videos, MSDN documentation, MSDN forums FAQs, Code samples, and additional guidance.

Once the introductory material is completed. Developers can get up to speed by working through these exercises:

1. Request an integration sandbox account from Partner Center
2. Request an App ID and client secret from Partner Center
3. Build and run the CSP sample code from GitHub
4. Build and run an Azure AD sample from GitHub
5. Run a network trace and monitor the HTTP request and response

Most partners who are integrating with the CSP APIs have an existing customer portal system that they sell to customers with. This customer portal may be linked to other internal systems such as an ordering system and a billing system. These existing systems need to work with an interface module that connects to the CSP APIs as shown in the following diagram.

A project plan for the integration work should include the following steps:

1. Training time for developers on new tools and technologies
2. Document system architecture of existing customer portal and associated systems
3. Plan for CSP API integration points
4. Review system architecture changes and improve
5. Build out code proof of concept using CSP Integration Sandbox
6. Review proof of concept code and improve
7. Build solution

To determine how much work will be required for this integration we recommend you have the team that would be doing the coding development time estimate the above integration work. Development teams should consider the integration interface module, any changes to your ordering and billing systems, any training or new technologies that they aren’t familiar with and also time for integration testing.

When troubleshooting a CSP API integration issue use some of the following guidance to identify and resolve the issue you are seeing.

1. Become familiar with and handle all the error conditions from the CSP APIs. These are well documented in the MSDN documentation and most CREST API errors also return a JSON error structure with details of the error.
2. Get the HTTP layer REST message request and response from the code that you are running and validate that against the sample messages in the MSDN documentation. You will also need these requests and responses logged in case you submit a post to the MSDN forum or to Microsoft support.
3. Use the provided C# sample code and replicate the scenario with that. Do this even if you don’t regularly use C#. Replicating the scenario in this simple code base will allow you to see what REST code is sent to Microsoft when the scenario is working. Of if it doesn’t work with the sample code, you will have more information about the problem you are encountering.
4. Post your request on the MSDN forums and include your scenario, your code snippet, and the HTTP log of your request and response. Make sure to remove your client secret from the sign-in request if you are including that to avoid security issues.
5. You can use break fix support from the Partner Center web portal. This is available if you have something that you built and it was working, you changed nothing, and it appears that the Microsoft end of the integration stopped working. When you access break fix support it directs you to the Office 365 admin portal and be sure to select Partner Center APIs as the category of the support request.
6. You can use MPN partner benefit support incidents for API on-boarding assistance to ask for help with doing API integration.
7. You can also use Microsoft Premier Support hours to similarly ask for API on-boarding assistance.

Purpose: For creating and editing new customers and for provisioning new subscriptions to those customers.

Intro onboarding video: https://youtu.be/8RRssasC2Ys  
MSDN Documentation: https://msdn.microsoft.com/en-us/library/partnercenter/dn974944.aspx  
MSDN Forums: https://social.msdn.microsoft.com/Forums/en-US/home?forum=partnercenterapi  
Code samples: https://github.com/PartnerCenterSamples/Commerce-API-DotNet/  
MSDN Forums FAQ: https://www.microsoft.com/en-us/download/details.aspx?id=48218  

Purpose: Partners can get a list of their customers, a list of each customer’s users, can add and edit user details, can assign Office 365 seat licenses to specific users, and can add users to the admin group such that they can use the Azure management portal.

MSDN Documentation: https://msdn.microsoft.com/en-us/library/azure/hh974476.aspx  
MSDN Forums: https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=WindowsAzureAD  
Code samples: https://github.com/AzureADSamples/ConsoleApp-GraphAPI-DotNet

Purpose: Partners can review near real time Azure service usage data from the Usage APIs and can lookup service costs per datacenter and date range with the rate card APIs.

Overview: https://azure.microsoft.com/en-us/documentation/articles/billing-usage-rate-card-overview/  
MSDN Documentation: https://msdn.microsoft.com/en-us/library/azure/mt218998.aspx  
Sample code: https://github.com/Azure/BillingCodeSamples  

Purpose: Once the Azure subscription is setup you may want to provision specific services and administer them.

MSDN Documentation: https://msdn.microsoft.com/en-us/library/azure/dn578292.aspx 

Purpose: To administer an Office 365 tenant that has been set up. For example to set a mailbox quota.

Documentation: https://dev.office.com  

Partner Center - https://partnercenter.microsoft.com

Microsoft Message Analyzer https://technet.microsoft.com/en-us/library/jj649776.aspx 

Telerik Fiddler http://www.telerik.com/fiddler

POSTMAN https://www.getpostman.com

• Anonymous
  October 10, 2015
  The comment has been removed