Use partner benefits in other tenant

Lesedauer 5 Minuten

Microsoft partners are not only allowed to provide licenses to their customers but also receive free licenses for their own use—known as Partner Benefits—depending on their status. These licenses may be used not only in the partner’s tenant but in all tenants owned by the company. Accordingly, some of the licenses can also be used for other purposes if not all benefits can be put to good use in the production environment.

However, those accustomed to the previous procedure for redeeming benefits may initially find the new fiscal year confusing (the old procedure may still work for now, but a transition to the new system is definitely underway). Therefore, this article explains the new procedure for redeeming Partner Benefits in a different tenant.

The previous procedure

In recent years, the process for redeeming partner benefits has been as follows:

Depending on how far along Microsoft is with the transition of partner accounts, this process may still be available. However, it will soon be replaced by a new process that, in principle, simplifies the procedure.

The new procedure

Under the new process, benefits are no longer redeemed using product keys. Instead, redemption is done through a so-called billing profile, which can be viewed via the Azure portal: Cost management + billing - Microsoft Azure.

If the partner tenant and the production tenant are the same, no additional steps are required. In this case, redeeming benefits is greatly simplified, as there is no need to enter a product key separately via the website. However, if the partner tenant and the production tenant are separate (as required by Microsoft) or if benefits are to be redeemed in a third tenant (e.g., development, testing, etc.), then the steps described in the following chapters must be followed.

Information

Is it even allowed to use these benefits in a different tenant?
Yes! Microsoft expressly allows this, provided that the tenants are linked via a billing account. The only restriction is that all tenants must belong to the same company. See View and Use Your Cloud Services Benefits - Partner Center | Microsoft Learn

Prerequisites

The following is required for configuration:

Partner tenant:

  • User account with the “Billing Administrator” role or higher
  • User account with the “Microsoft AI Cloud Partner Program Partner Admin” role for access to the “Benefits” section in the Partner Center

Target tenant for redemption:

Warning

Microsoft sometimes deviates from best practices in the context of its partner program. Ideally, there should be no administrator accounts with active mailboxes. Unfortunately, the workaround using a “+” address does not work in this case. Therefore, there are two ways to address this requirement:

  • The administrator account being used is temporarily assigned an Exchange Online license for the configuration (recommended)
  • The user in question is temporarily assigned the “Global Administrator” role for configuration purposes

Configuration

If all requirements are met, proceed as follows.

Associate billing tenant

First, you must assign the tenant in which the benefits are to be redeemed via the Azure portal:

If there are multiple billing scopes, you must first identify the correct one. You can verify this using the ID you noted earlier, which appears below the billing scope in the “Billing > Billing Profiles” menu. If the ID does not match, select a different billing scope.

  • In the correct billing area, click “Quick Access > Access Control (IAM)” in the menu on the left
  • Click “Associated billing tenants” at the top
  • Click “+ Add” at the top—a new menu will open on the side
  • Enter the tenant ID of the target tenant and assign any display name (e.g., “Contoso - Development”), check both options at the bottom, and click “Add”

The target tenant is now associated.

Setting up access for partner tenant

Next, a user from the target tenant must be invited who has the permission to grant access to the target tenant's billing profile. The “Global Administrator” role is required for this. The invited user will also receive an email containing a link that must be used to confirm access.

  • Below the billing section, click “Quick Access > Access Control (IAM)” again
  • Click “+ Add” at the top—a new menu will open on the side
    • Role: “Billing Account Owner”
    • Tenant Name: “”
    • Users, Groups, or Apps: “”
    • “Add”

Once the user has been successfully added, they should receive an email.

Setting up access for target tenant

The email contains a link that must be opened by the user from the target tenant. This opens the Azure portal in the target tenant.

(Note: In my case, the request has already been confirmed, so the options in the image are grayed out.)

  • Review the requirements
  • Check the box next to “I understand that…” and click “Approve” at the bottom


This allows the target tenant to access the partner tenant's billing profile.

Transferring a subscription

The desired benefits can now be redeemed. By default, these are always redeemed in the tenant through which the benefits are available. However, this is not a problem. By assigning the other tenant, it is possible to transfer the redeemed benefits to that tenant. To do this, follow these steps:

  • Open product overview in the Microsoft 365 Admin Center
  • If the redeemed benefit is not yet visible, select the account in which the benefit was redeemed by clicking the “Change Billing Account” button at the top (highlighted in blue).
  • Select a benefit from the list—a new page will open
  • Click the blue link “Move to another tenant”
  • Select the desired destination client from the list and click “Move subscription” at the bottom


The subscription will now be moved to the target client and should be available there within one minute. If the subscription was accidentally moved to the wrong client, it can be moved back to the partner client at any time and then moved again from there.

Achtung!

Once a user has been assigned to a subscription, that subscription can no longer be moved and is permanently assigned to that tenant. This remains true even if all assignments are removed from the subscription. Therefore, before assigning users, you should make absolutely sure that the subscription is assigned to the correct tenant!



Liked this article? Share it!