class="news-template-default single single-news postid-2553 wp-custom-logo tribe-no-js">
When is a MCA not a MCA?
IMO TLAs were presumably introduced to save time or precious keystrokes – but sometimes, they just cause more confusion – sometimes we need clarity in what they stand for.
TLA’s can be confusing at the best of times, but when you replace one TLA with another TLA, that has exactly the same 3 letters, in the same order, but means something very different – it is surely bound to lead to confusion?
I mean really? OMG, EIE… like WT*?
IMO TLAs were presumably introduced to save time or precious keystrokes – but sometimes, they just cause more confusion – sometimes we need clarity in what they stand for.
TLA’s cBST, this is effectively what Microsoft have done with the MCA. I am sure it was sanity checked and approved at multiple levels by workshop groups, change adoption specialists and other highly intelligent & highly paid people. I am sure it made perfect sense to them and they can see no reason for this to cause confusion for anybody – but the reality is for mere mortals like me, surely it would have made more sense to use 3 different letters or at least change the order of them so make it easy to differentiate between them?
Anyway, what am I ranting about? I am ranting about the fact that Microsoft have effectively replaced the Microsoft Cloud Agreement (MCA) with the Microsoft Customer Agreement (MCA).
These are two separate agreements and mean different things. However, they are both very important agreements and they should not be confused.
The Positive
Naming convention asides, the (new) MCA is not a bad thing. It is in fact a positive step. The Customer Agreement is an important part of helping customers with progressing and maintaining their digital transformation in an ever-changing world.
The agreement helps simplify the terms under which customers agree to purchase and consume MS products and services. It is a non-expiring contract and the agreement updates dynamically as products are added to the customers portfolio.
As of Feb 1st 2020, any customers wishing to transact new CSP business or to manage existing subscriptions must first complete the (new) MCA.
If you are a MicroWarehouse partner and are providing CSP to your customers, there is a DIY option, you can complete the MCA details for your customer in our CSP cloud portal.
Just click on Manage beside the customer in question, scroll down to the Microsoft Customer Agreement and populate the fields with the required info of the contact within the end-customer agreeing to the MCA – and then hit save.
You should then be able to proceed to adding new services or making changes for your customer.
Full details on the Microsoft Customer Agreement are available here.
Well PPL, I’ve GtG, but please LAM if you want – but if you do, please do me a favour – in fact, do us all a favour and write full words with full sentences, so we can all understand first time and we don’t have to spend hours on the internet trying to decipher TLA BS.n be confusing at the best of times, but when you replace one TLA with another TLA, that has exactly the same 3 letters, in the same order, but means something very different – it is surely bound to lead to confusion?
By Rob Driver.