We'd like to flag or not have OSU start tracking the usage for entitlements that have less than 150 entitlements (requirement). For example, if a customer 1000 seat customer has 10 licenses of EMS E3 and they are testing Intune and they deploy the 10 entitlements, the usage will be 100% and we would NOT be eligible for any incentives when the usage is already at 100% and we submit a CPOR claim. This is common especially with CSP customers who do not want to invest in the cost of the entire license cost while they are testing. It's challenging to track to watch when the customer will make the rest of the license purchase when you have hundreds of customers. Changing the tracking of customers with less than 150 entitlements will allow partners to assist customers with less than the 150 requirement with the intent to purchase more after testing is complete.
Status details
2021-08-06 - Assignment Team - Assigning to Partner Support Team to Triage2021-08-21 - EPX - We are validating with OSU the process and impact of claiming workloads with less than 150 PAU and associated usage at time of claim. Once this is understood will share and address the request for a flag or other indication.
2021-09-08 - EPX - Below is the update on customer workloads below 150 seats for CPOR claims and ways to address claims for these type of customers.
- A customer has to have a 150 seat minimum in order for partner to be eligible to earn incentives, eligibility will not start unless this is met. Usage prior to 150 PAU will not count.
- If a partner is told their AU at time of claim was too high and they know their customer had fewer than 150 licenses, there are two things that partners can do in these situations.
- If AU % goes down after the proof of concept and seat count over the 150 seats partners could disassociate themselves and re-claim becoming eligible. Example: AU% goes down to 8% after the first seat deployment over 150, they dissociate themselves, re-claim and mention in the comments that they are doing this due to a bug showing them ineligible incorrectly.
- Alternatively, partners can wait after the seat deployment over 150 seats for AU% to reach 40% and reach out to support for payment via exception on both milestones. In that case: I’d mention this: “We started working with our customer in the month of x (see attached POE) on claim xxx and had a low seat count of <150 seats under the initial pilot/proof of concept. When claiming in Partner Center, usage was already above milestone eligibility at x% which left us ineligible to earn. Can you log a policy exception so that we can be considered eligible given we engaged with this customer before they had any usage?"
There are 2 issues:
1. When a claim in OSU is approved with less than 150 licenses it will not be provisioned in FTOP.
2. In this example it means we hit 100% usage based on 10 entitlements. When the customer adds more licenses over 150 this workload is not eligible anymore for the step-up. So we will not get an incentive paid for he effort we deliver to deloy. This is an error in the current T&C and should be fixed.
Once customer purchase more seats and goes into another size, like XS, S, M and so on.. it will be eligible for incentives, the delta between XXS and the new size, which will be 100% of the payment you should receive anyway.
It is confusing, but I understand the logic and work accordingly.