Clarification Request: MAICPP Credit Delegation, Visibility, Activation, and Alerting Limitations

Question

Context:
We have migrated from legacy Gold Membership to the Microsoft AI Cloud Partner Program (MAICPP) and are trying to implement an operational model for managing MAICPP support credits / Azure credits with appropriate delegation, monitoring, and alerting.

Objectives:

1. Delegate credit consumption to a single account/subscription.
2. Delegate administrative visibility so more than one person can monitor usage and manage benefits in Partner Center.
3. Implement proactive monitoring/alerts for credit usage thresholds to avoid accidental expiry or overrun.

Questions:

• Is usage visibility constrained to the Partner Center Benefits workspace (we did not find documented support for exporting usage, APIs, or integrating with Azure Monitor/Cost Management alerts)?
• We found conflicting information on transferring credit usage permissions. Some documents state we can transfer credit usage to users/subscriptions while other documents state reassignment is only permitted after benefit year is finished. If we were to wait for this would we lose the credits, as they must be consumed within a year? What are the limitations on transferring credit usage/management permissions once benefit year has begun?
• Credits have no yet been activated and have passed the 90 day window, can they be activated once this window has passed?
• We have three separate benefit packages, is it possible to transfer all credits to a single subscription to allow for easier usage monitoring?

Answer 1

1. Usage Visibility: Currently, usage visibility is primarily constrained to the Partner Center Benefits workspace. There is no documented support for exporting usage data, APIs, or integrating with Azure Monitor/Cost Management alerts for monitoring credit usage.
2. Credit Usage Permissions: There is conflicting information regarding the transfer of credit usage permissions. While some documents indicate that credit usage can be transferred to users or subscriptions, others specify that reassignment is only permitted after the benefit year has concluded. If you wait until the benefit year ends to transfer credits, you may risk losing the credits if they are not consumed within the one-year period from the start date.
3. Activation of Credits: If the credits have not been activated and the 90-day window has passed, they generally cannot be activated once this window has elapsed. It is advisable to activate credits within the specified time frame to avoid loss.
4. Transferring Credits: Regarding transferring credits from three separate benefit packages to a single subscription, the ability to do so may be limited. Typically, credits are tied to specific subscriptions and may not be easily consolidated across different benefit packages.

For specific details on your situation, it's best to consult the official documentation or reach out to Microsoft support for guidance on managing your credits effectively.