Question regarding BTTC2 Promotion - 2nd BTTC2 subscription possible?

[JensH20457]

One of our Dynamics 365 Business Central on-premise customers has switched to SaaS and used the BTTC2 promo. Now another Dynamics 365 Business Central on-premise customer (with a separate on-premise license), who is connected to the first customer as defined by Microsoft, also wants to switch to SaaS and asks whether he can use the BTTC2 Promo on the same tenant. Can anyone answer this question? Technically it is possible to create a second BTTC2 subscription for the tenant. But is it also ok in terms of licence law?

[#2]

Hi @JensH20457 

Thank you for posting to the community!

Per the information provided in your previous post on this topic, Promo Bridge to the Cloud 2: Possible if another subsidiary has licensed BC in the same tenant? - Mi...

The BTTC2 promo is intended for customers committed to migrating to the cloud, so in general terms and based on the reply on the previous post (in the link above), the 2nd customer should be eligible to apply for this promo. However, when you submit the documents to your local ROC (per the instructions to apply for this promo), your local ROC will confirm:  see the BTTC2 FAQ for details:

If this reply answers your question, please Accept as the solution to help the other members find it more quickly. Otherwise, if after reviewing the information you have additional questions, please let me know.

Regards,

Microsoft CSP Licensing Concierge

[#3]

Does this mean, that the 2nd customer can use the BTTC2 promotion, even if it is the same tenant?

[#4 · Accepted solution]

I do not believe there are any issues creating new subscriptions, but you still must gain approval from your ROC for the customer's eligibility for the promo and provide the evidence.

Having different subscriptions would make this easier.

Total value for Subscription 1 >= Annual EP for Customer 1
Total value for Subscription 2 >= Annual EP for Customer 2

I would suggest your ROC would be able to provide the best view on this.