Azure Subscriptions

The Azure Subscriptions page in MSPControl is used to manage Azure subscriptions connected to the current Azure plan. This area allows administrators to review all subscriptions under the selected Azure plan, open a subscription record, maintain budget and alert settings, and assign Azure roles to users for that subscription.

Because Azure subscriptions are one of the main operational containers for Azure resources and billing scope, this page is important for administrators who need visibility into subscription-level settings, security assignment, and notification behavior inside MSPControl.

Table of Contents

• Azure Subscriptions Overview
• Azure Subscriptions List Page
• Azure Subscriptions Table Columns
• Azure Subscription Details
• Subscription Roles for Users
• Add Role Assignment
• Page Actions
• Best Practices

Azure Subscriptions Overview

The Azure Subscriptions page displays subscriptions linked to the currently selected Azure plan. The page title includes the Azure plan identifier, which helps administrators confirm the exact plan context before reviewing or editing subscription records.

This page is especially useful in organizations where multiple Azure subscriptions exist under one Azure plan. It gives administrators a centralized way to review subscription names, IDs, and status values before opening the full subscription configuration page.

Azure Subscriptions List Page

The main Azure Subscriptions list page displays all subscriptions associated with the current Azure plan in a table. It also provides tools for creating a subscription record, searching the list, and adjusting column visibility.

Azure Subscriptions Page Controls

1. Create Subscription opens the workflow for adding or registering a new Azure subscription under the selected Azure plan.
2. Category Filter allows administrators to narrow the list using the available dropdown options.
3. Search helps locate a specific subscription by name, ID, or other searchable values.
4. Column Visibility allows administrators to control which columns are displayed in the table.
5. Page Size Selector controls how many subscription rows are shown at one time.

Azure Subscriptions Table Columns

1. Friendly Name shows the readable name of the Azure subscription.
2. Subscription ID shows the Azure subscription identifier.
3. StatusStr shows the current subscription status. In the example shown, the values are active.

This overview is useful for quickly confirming which subscriptions exist under the plan and whether they are currently active before opening an individual record.

Azure Subscription Details

When a subscription is opened, MSPControl displays a dedicated Azure Subscription page with the main subscription properties, budget controls, notification settings, and user role assignment area.

Azure Subscription Fields

1. Azure Plan ID shows the Azure plan identifier associated with the subscription.
2. Subscription ID shows the Azure subscription identifier. Both ID fields include copy controls, which makes them easier to reuse in administrative workflows.
3. Subscription status shows the current status of the subscription. In the example shown, the status is active.
4. Subscription Name shows the friendly subscription name.
5. Subscription Started shows when the subscription started.
6. Subscription Suspended stores the suspension-related value or date if the subscription has been suspended.
7. Subscription Security Contact Emails stores the email addresses that should receive security-related notifications for the subscription.
8. Azure Budget defines the budget threshold for the subscription. In the example shown, the value is entered in USD.
9. Send Budget Exceeded Alert defines how the exceeded-budget alert should behave. In the example shown, the value is System Policy.
10. Send Budget Warning Alert defines how warning-level budget alerts should behave. In the example shown, the value is also System Policy.
11. Send Azure Advisor Report controls whether Azure Advisor reporting should be enabled for the subscription.
12. Azure Advisor Report Email stores the email address or addresses that should receive the Azure Advisor report.

This section combines identity, lifecycle, alerting, and reporting settings for the subscription. It is especially useful for operational control, subscription-level financial visibility, and security communication.

Subscription Roles for Users

The Subscription Roles For Users section is used to manage Azure role assignments for users within the current subscription. This allows administrators to define who should receive access to the subscription and at what permission level.

The section includes a list view with filtering, search, column visibility, and an action to add new role assignments. This makes it possible to treat Azure access as part of the subscription record itself rather than managing it separately elsewhere.

Subscription Roles For Users Controls

1. Add Role Assignment opens the role-assignment window.
2. Category Filter allows the current assignment list to be narrowed using the available dropdown options.
3. Search helps find a user or role entry inside the assignment list.
4. Column Visibility allows administrators to choose which columns are shown in the assignments table.
5. Page Size Selector controls how many assignment rows are displayed at once.

Subscription Roles For Users Table Columns

1. User shows the assigned user.
2. Role shows the Azure role assigned to that user.
3. Action provides row-level actions for managing the assignment.

This table is used to review and maintain subscription-specific access permissions.

Add Role Assignment

When administrators click Add Role Assignment, MSPControl opens the assignment window used to connect a user with an Azure role in the current subscription.

Add Role Assignment Fields

1. User allows the administrator to select the user who should receive the role assignment.
2. Role allows the administrator to select the Azure role to assign. In the screenshot, the list includes options such as Contributor, Owner, Reader, and additional Azure service roles.

This makes the feature flexible enough to support both broad and narrow Azure permission models depending on the organization’s access requirements.

Add Role Assignment Usage

The role picker suggests that MSPControl supports standard Azure RBAC-style role assignment inside the subscription context. This is useful because subscription access often needs to be granted differently for administrators, readers, contributors, or service-specific operators.

By assigning roles from this page, administrators can connect Azure access directly to the relevant subscription record, which helps keep access review more organized.

Page Actions

1. Cancel closes the subscription page without saving the current changes.
2. Save Changes and Exit saves the changes and returns to the previous page.
3. Save Changes saves the changes without leaving the page.

Because subscription settings can affect cost visibility, alert routing, and Azure access, administrators should review all changes carefully before saving.

Best Practices

• Verify the Azure Plan ID and Subscription ID before editing settings so changes are made to the correct subscription.
• Keep Subscription Security Contact Emails current so security-related notifications reach the right people.
• Use the Azure Budget field together with warning and exceeded-budget alerts to maintain better financial visibility.
• Use System Policy options only when the organization wants subscription behavior to follow broader MSPControl policy settings rather than a custom override.
• Enable Send Azure Advisor Report only when the subscription needs recurring advisory reporting and there is a clear recipient list.
• Assign Azure roles carefully and follow least-privilege principles, especially for high-impact roles such as Owner and Contributor.
• Review existing role assignments regularly to make sure user access still matches operational responsibility.
• Use the subscription list page as a quick validation point to confirm subscription status and identity before opening or editing a specific record.