Action Required: Microsoft Customer Agreement (MCAv2) in the CSP Program
Update: The Go Live of MCAv2 in rhipe PRISM portal has been moved from December 1, 2019 to December 13, 2019
Microsoft introduced the Microsoft Customer Agreement (MCAv2) on October 1, 2019. The Microsoft Customer Agreement is a simplified purchase agreement that provides consistent purchase terms for customers – regardless of the way customers choose to buy.
An existing customer can still transact under the Microsoft Cloud Agreement (MCAv1) during the transition period before MCAv2 becomes mandatory on January 31, 2020. If you have a new customer buying through rhipe, they can continue to accept MCAv1 between now until December 12, 2019. On December 13, 2019, rhipe PRISM portal will be transitioning from accepting the MCAv1 to MCAv2 and only MCAv2 will be accepted from then on.
This blog will provide an overview of the important information for rhipe CSP indirect resellers, what the new Microsoft Customer Agreement is and what are the important dates to keep in mind when presenting this to your end customers.
What is Microsoft Customer Agreement?
The new Microsoft Customer Agreement is a contractual agreement between the end customer and Microsoft, which is meant to streamline the purchasing terms for end customers, regardless of the way channels and partners the customer are buying from. In the CSP program, the new agreement will essentially replace the current Microsoft Cloud Agreement, previously introduced back in November 2018.
You can review the Microsoft Customer Agreement today at http://aka.ms/customeragreement.
How is the new Microsoft Customer Agreement different from the Microsoft cloud agreement?
Microsoft Cloud Agreement (MCAv1) is the current customer agreement that a customer accepts from Microsoft. However, a customer will need to sign multiple MCAv1 if they are purchasing through multiple CSP partners. They will also need to accept multiple agreement from Microsoft if they are purchasing through multiple licensing channels.
The Microsoft Customer Agreement (MCAv2) is the replacement agreement for the CSP customers. Once signed, there is no expiration or renewal of agreement requirement. It is portable, as it can be used by customer for purchasing of licenses across multiple Microsoft licensing channels.
What do I need to do to prepare for MCAv2 as a Partner?
Before MCAv2 is available in PRISM Portal on December 13, 2019, you will be asked to continue doing the current MCAv1 Partner Attestation through PRISM portal, just as what you have been doing today. Once MCAv2 is available on December 13, 2019, you can only attest the acceptance of MCAv2 by your customers.
For existing customers in PRISM, you can continue to add and edit the subscription for them under rhipe CSP like what you are doing today. Having said that, it is recommended that you present a copy of the MCAv2 to your customer so that you can attest that they have accepted MCAv2 in PRISM portal starting December 13, 2019.
For new customers, attest acceptance of MCAv1 before December 13, 2019, or MCAv2 starting December 13, 2019 to add new subscriptions. Therefore, we highly recommend you to ask your customers to accept both MCAv1 and MCAv2.
What you should do on during the transition period and when MCAv2 becomes mandatory milestones?
|Important Dates||Activity||What is required from you?|
|December 13, 2019||MCAv2 becomes available for partner attestation through PRISM Portal||
|Early January 2020||Partner can invite their customers via a URL to review and accept MCAv2 in Microsoft Admin Center||
|January 31, 2020||Microsoft Cloud Agreement (MCAv1) no longer available for purchasing in CSP||
How do my customer accept the new Microsoft Customer Agreement (MCAv2)?
Since the confirmation of the MCAv2 is the responsibility of the partner, the above question becomes very relevant to this blog. To make things simple, rhipe PRISM portal would provide you with a URL to invite your customers to review and accept MCAv2 in Microsoft Admin Center. The detailed process of Microsoft customer agreement acceptance consists of two stages which are as following:
- Partner Attestation of MCAv2 from December 13, 2019 in PRISM Portal
- Partner fills in the Information required in Prism: First name, last name, email, signing date and optionally phone number.
- Partner proactively keeps the record of the information which is also available in PRISM.
- Available from early January 2020, partner can also invite their customers via a URL to review and accept the Microsoft Customer Agreement in Microsoft Admin Center. The link can be obtained in PRISM portal.
- Partners will be notified once MCAv2 is accepted. (Details to follow)
- Subscription can be created once customer has signed the MCAv2.
- Partner can also check and see whether customer has signed MCAv2 before. If yes, then can provision subscription without needing customer to sign MCAv2 again.
- Partner attestation option in PRISM portal will continue to remain available.
Can I still use the current Microsoft Cloud Agreement (MCAv1)?
You can use the current Microsoft Cloud Agreement (MCAv1) attestation until December 12, 2019. On December 13, 2019, rhipe PRISM portal will be transitioning from accepting the Microsoft Cloud Agreement to Microsoft Customer Agreement. Only the Microsoft Customer Agreement (MCAv2) will be accepted.
Your existing customers who have accepted the MCAv1 can continue to add/edit/renew subscriptions through CSP until January 31, 2020, unless they want to order the new Azure Plan. They must accept the MCAv2 after January 31, 2020 to continue adding/updating/renewing CSP subscriptions through you.
Where can partners or customers review the most current version of the Microsoft Customer Agreement (MCAv2)?
The most current version of the MCAv2 for viewing and download at http://aka.ms/customeragreement.
For more information around the Microsoft Customer Agreement (MCAv2), please reach out to your respective rhipe Account Manager. Also, check out the FAQ which gives details around Microsoft Customer agreement.
This blog is brought to you by Mikki Chopra from the Strategy and Enablement Team.
If you have any question, please contact him at Mikki.firstname.lastname@example.org