VPC Service Controls provides additional security for the Managed Service for Microsoft Active Directory
service and its resources. For more information, see
[VPC Service Controls](https://docs.cloud.google.com/vpc-service-controls/docs/overview.md.txt).

## Additional configuration

Enabling on-premises access to Managed Microsoft AD API and using a
Shared VPC with the Managed Microsoft AD domain require additional
configuration.

### Enabling on-premises access to Managed Microsoft AD API

To enable on-premises access to the Managed Microsoft AD API, you must
[set up private connectivity](https://docs.cloud.google.com/vpc-service-controls/docs/set-up-private-connectivity.md.txt).

### Using a Shared VPC

When using a [Shared VPC](https://docs.cloud.google.com/vpc/docs/shared-vpc.md.txt), the Managed Microsoft AD domain must be created in
the host project and the Shared VPC network host must be located within the same
service perimeter as the projects connected to the network.

For information about how to deploy Managed Microsoft AD with cross-project
access using Shared VPC, see [Deploy Managed Microsoft AD with
cross-project access using domain
peering](https://docs.cloud.google.com/managed-microsoft-ad/docs/shared-vpc-managedad-cloudsql).

## What's next

- Learn more about the [VPC Service Controls support for Managed Microsoft AD](https://docs.cloud.google.com/vpc-service-controls/docs/supported-products.md.txt#table_managed_ad)