Recommended Reading: What is a Subscription?
This article explains how to provision a Subscription for an Organization.
Note: There are two types of Subscriptions available:
1. The standard “Pay-as-You-Go” Subscription
2. Dev/Test Subscription.
Note: The Provisioning Entity that the Organization belongs to must be enabled for Dev/Test Subscriptions. Dev/Test Subscriptions have their own unique requirements that must be adhered to.
1. Log in to the Nebula UI and click on Organizations:
2. The Organizations page will be displayed. Locate the Organization where you want to add a Subscription. Click on the cog in the Actions column, and select “Manage Subscriptions”:
3. The Manage Subscriptions dialog will be displayed. Click “Add Subscription”:
4. The Add Subscription dialog will be displayed:
5. Enter an optional description in the Description field and the email address associated with whoever will be the owner of the subscription:
Email Address Must Represent a Specific AAD User: The email address of the Subscription Owner entered in this step must be tied to an individual Azure Active Directory user. You cannot assign a Subscription to an AAD Basic Group with multiple members.
From a security perspective, it is recommended that the email address be a local/member Azure Active Directory user, instead of type Guest. This ensures that if the user leaves the Organization or Azure Active Directory, no access to the subscription remains.
6. Tick the Dev/Test Subscription box if the Subscription meets the Dev/Test requirements. You can click on the ‘Special Legal User Requirements Apply’ link to review the requirements. If you tick the Dev/Test Subscription box, the dialog will expand with a warning and an additional tick box indicating that you have read and understood the Dev/Test Subscription policy:
Important Note: If you provision a Dev/Test Subscription, it cannot be undone. There is no way to convert a Dev/Test Subscription to a standard Pay-as-You-Go subscription. Dev/Test subscriptions are exclusively for the development and testing of your applications. Usage within the subscription does not carry a financially-backed SLA, except for use of Azure DevOps and Visual Studio App Center.
7. You can optionally click on the “Add Tags to Subscription” button, which will further expand the dialog. You can create Tags by entering a Key/Value pair, and then clicking Add Tag:
8. Once you have added the desired Tags, verify that the email address is correct, and click the box indicating that the email address is accurate. Then, click Submit:
9. The UI will display a message indicating that the operation was successful:
10. The page will be updated to show the subscription and the status column will indicate that it is being provisioned:
If the Description is greater than 40 characters long, the “Information” icon will be displayed. Hovering your mouse over the icon will display the entire description:
The email address used to provision the subscription must have access to the Azure Active Directory where the subscription will be transferred for use.
For further information on viewing Subscriptions, see How Do I View Subscriptions for an Organization?
For instructions on transferring a Subscription, see How do I Transfer an Azure Subscription to the Target Azure Active Directory?
For instructions on moving a Subscription to a different Organization, see How Do I Move a Subscription to a Different Organization?
11. Once the Subscription has been provisioned, the system will send an automated email to the email address that was entered as the Subscription owner.
This email will provide instructions for the owner to transfer the subscription as described in this article:
How do I Transfer an Azure Subscription to the Target Azure Active Directory?
Note that the UI will indicate how many subscriptions have been allocated to an Organization through the “Active” column on the Organizations page. The icon appears as a checkmark, with a number indicating how many subscriptions are allocated: