Entra ID Domain Service

The Entra ID Domain Service page in MSPControl is used to prepare and create the Azure-side configuration for a managed domain service connected to the current organization. This page focuses on infrastructure choices such as the resource group, managed domain, Azure location, virtual network, and subnet layout.

This page is part of Organizations > Azure > Entra ID Domain Service. It is also the destination opened from the Domains area when administrators need to move from domain allocation into Entra ID domain service setup. Because these settings affect Azure network structure and managed domain placement, the values should be reviewed carefully before creating the service.

Table of Contents

• Entra ID Domain Service Overview
• Page Fields
• Virtual Network Parameters
• How Virtual Network Selection Works
• CreateDomainService Action
• How Entra ID Domain Service Fits into MSPControl
• Best Practices

Entra ID Domain Service Overview

The Entra ID Domain Service page is a setup screen for defining where the service should be created and how its supporting network structure should look. It combines Azure infrastructure choices and managed-domain settings in one place, which makes it easier to prepare the environment without switching across multiple pages.

In the example shown, the page is being used with Create New Virtual Network selected. That is why the additional Virtual Network Parameters section is visible. This means the page can support both reuse of existing Azure networking and creation of new network components from within the same workflow.

Page Fields

1. Resource Group defines the Azure resource group where the domain service resources should be placed. This is important because the resource group controls how related Azure resources are organized.
2. Managed Domain defines the domain name that will be used for the managed domain service. This is the domain context the service will be associated with.
3. Azure Location defines the Azure region where the service should be deployed.
4. Virtual Network defines whether the service should use an existing virtual network or create a new one. In the example shown, the selected option is Create New Virtual Network.

These fields define the main deployment context. Before proceeding, administrators should make sure they are working in the correct Azure region and using the intended managed domain and resource group.

Virtual Network Parameters

When a new virtual network is being created, MSPControl displays the Virtual Network Parameters section. This section is used to define the network structure required for the domain service.

1. Virtual Network Name defines the name of the new virtual network.
2. Virtual Network Address Space defines the overall address space for the virtual network.
3. Domain Service Subnet defines whether the domain service should use an existing subnet or create a new one. In the example shown, the selected option is Create New Subnet.
4. Domain Service Subnet Name defines the name of the subnet used for the domain service.
5. Domain Service Subnet Address Range defines the subnet address range reserved for the domain service.
6. Workload Subnet Address Range defines the address range used for workloads alongside the domain service network design.

This section is especially important because network design choices made here affect how the managed domain service will fit into the broader Azure environment.

How Virtual Network Selection Works

The Virtual Network dropdown determines whether MSPControl should work with an existing Azure virtual network or build a new one as part of the setup. When an existing network is selected, administrators would use the already prepared Azure network structure. When Create New Virtual Network is selected, MSPControl exposes the additional network parameters needed to define the virtual network and subnet values directly on this page.

The same logic applies to the Domain Service Subnet selection. If a new subnet is being created, MSPControl asks for the subnet name and address range. This makes the page flexible enough to support both fresh deployments and environments where the Azure networking already exists.

CreateDomainService Action

The CreateDomainService button starts the domain service creation process using the values entered on the page. This is the final action that tells MSPControl to use the selected Azure and network settings for the new service.

Before clicking this button, administrators should confirm that the resource group, domain, region, virtual network choice, and subnet values all match the intended Azure design.

How Entra ID Domain Service Fits into MSPControl

This page connects domain management with Azure infrastructure setup. Earlier in the workflow, domains can be prepared and allocated in the appropriate organization context. This page then takes that domain-related context and applies it to the Azure-side managed domain service configuration.

That makes the Entra ID Domain Service page an important bridge between hosted-organization domain planning and actual Azure deployment. It keeps managed-domain setup tied to the organization rather than leaving it as a separate undocumented Azure task.

Best Practices

• Verify the Resource Group, Managed Domain, and Azure Location before creating the service so the deployment is placed in the correct Azure context.
• Use clear naming for the Virtual Network Name and Domain Service Subnet Name so the network structure remains easy to understand later.
• Plan the Virtual Network Address Space and subnet ranges carefully so they fit the intended Azure network design.
• Make sure the Domain Service Subnet Address Range and Workload Subnet Address Range are consistent with the broader network plan before creating the service.
• Use an existing virtual network only when the Azure environment has already been prepared for this service and the network design matches the organization’s needs.
• Use the new virtual network option when the service needs a dedicated Azure network structure managed from this workflow.
• Review all values carefully before selecting CreateDomainService, because this page defines the actual deployment context for the managed domain service.