PAL and ISV

[ChristianFUMEY]

Hello,

As I just tested it in my own environment, it seems that an ISV running his SaaS offer, for example an add-on for Teams, on his own Azure subscription can add himself as PAL on his tenant.

Is it supported, and if yes what are the advantages:

 - ACR will count in Performance metrics for Cloud Platform and other Advanced Specializations ?

 - Partner will be eligible to Microsoft Commerce Incentives ?

Many thanks

[JanoschUlmer]

From technical perspective adding a PAL will count for competencies. However, I can not confirm currently that this is being considered as compliant. I will have a call next week with some folks internally to get clarification on this scenarios where the ISV is setting PAL for their own subscriptions. In some documentation it is said that Internal usage does not count, but there is some conflicting messaging around that.

What I can definitely say is that per current MPN Agreement Partners are not eligible to get Incentives for Internal usage - and if they get those accidentially Partner has to report to Microsoft and potentially pay them back. So a clear "No" here.

[ChristianFUMEY]

Hi Janosch,

The result of your next week call will be very interesting ! As in this case, this is not exactly for Internal usage but for hosting the SaaS App used by his customers. The ISV is using Azure, but he could also choose AWS or GCP. So any reward, at least Performance and best Incentives, would be great.

Or must he use a separate ''customer'' tenant, sell an Azure Plan to this ''customer'' to run his SaaS offer ? So he will be recognized for Performance and MCI.

[JanoschUlmer]

Hi @ChristianFUMEY  - just wanted to update you on the question reg. PAL tracking for internal Azure consumption of an ISV. It was confirmed now from MPN management that PAL tracking for this kind of consumption is not in compliance with the MPN terms - because internal usage is excluded. However, the team is looking at improving the options for ISVs reg. this in the future, it is a known gap in how the current competencies, policies and tracking systems work. 

[JanoschUlmer · Accepted solution]

it is internal from the perspective that the Partner/ISV is entered in the organizational information in the tenant, the Partner/ISV is the owner of the tenant. The ISV is acting as customer that agreed to the use terms for the Azure subscription. It is true that finally end customer is using their solution, still we would define it internal from a contract perspective.