In approx. 10% of the cases we get a notification of customer disassociation due to another partner claim for the same workload.
When we take a closer look at the impacted accounts we notice that:
- the accounts all have one global tenant ID;
- the accounts are active in several countries/global regions;
- the accounts don't work with a global deployment partner;
- the accounts work with several local partners depending on the region;
- the accounts deploy workloads at different speed.
In Azure it is possible to have multiple partners.
Why couldn't there be a similar solution to associate multiple partners when a customer is working with several local partners depending on the region?
When we take a closer look at the impacted accounts we notice that:
- the accounts all have one global tenant ID;
- the accounts are active in several countries/global regions;
- the accounts don't work with a global deployment partner;
- the accounts work with several local partners depending on the region;
- the accounts deploy workloads at different speed.
In Azure it is possible to have multiple partners.
Why couldn't there be a similar solution to associate multiple partners when a customer is working with several local partners depending on the region?
Status details
2021-04-19 - Assignment Team - assigning to Partner Support Team to triage.2021-05-11 - We hear you and have raised this issue with OSU and they have it in their backlog items to consider for future solutions. We will ensure this is on our list of items to revisit for FY22 and share the impact of this on partners with OSU.