> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/deployment/integrations/microsoft.md).

# Microsoft

### Secrets Management

StrongDM integrates with the Azure Key Vault to allow your nodes to proxy access to resources using secrets that are added and maintained in your cloud-native secrets manager.

{% content-ref url="/pages/JKdehtuOhm2FA2sGGP4Z" %}
[Azure Key Vault](/admin/access/secret-stores/azure-key-vault.md)
{% endcontent-ref %}

### Node Management

When configuring gateways or relays to proxy client traffic to resources, the Azure VM Nodes guide can be of use for setup.

{% content-ref url="/pages/tuEPiDGKs1TWfTSX5Og3" %}
[Azure VM Nodes](/admin/networking/gateways-and-relays/azure-vm-nodes.md)
{% endcontent-ref %}

### User Management

StrongDM provides an integration for SSO authentication with Entra ID as well as SCIM user provisioning with Entra ID.

{% content-ref url="/pages/8RmGtKC437c4uqq5hZzp" %}
[SSO With Microsoft Entra ID](/admin/principals/sso/entra-oidc.md)
{% endcontent-ref %}

{% content-ref url="/pages/SdEZR5fO7swT5G5GaQkR" %}
[Provisioning With Microsoft Entra ID](/admin/principals/provisioning/entra-provisioning.md)
{% endcontent-ref %}

### Resources

Additionally, StrongDM offers proxied access to cloud resources using the following resource types.

#### Cloud Resources

* Azure Cloud - Proxy access to manage your Azure cloud via the Azure CLI. See the [Azure Cloud guide](/admin/resources/clouds/azure.md) for more details.

#### Cluster Resources

When setting up Kubernetes, it's advisable to use a Helm chart and the Kubernetes (Pod Identity) resource type. If you're manually setting up a Kubernetes resource in the cloud, you can also use the Azure-specific AKS resource type.

* [Deploy Kubernetes via Helm chart](https://github.com/strongdm/charts/blob/main/deployments/sdm-relay/README.md)
* [Kubernetes (Pod Identity) resource guide](/admin/resources/clusters/kubernetes-podidentity.md)
* [AKS resource guide](/admin/resources/clusters/aks.md)

#### Server Resources

Any of StrongDM's SSH resource types (listed on the [Servers](/admin/resources/servers.md) page) can be used to set up AWS server instances as resources in StrongDM.

#### Datasource Resources

Several of StrongDM's datasource resource types can be used to set up resources within Azure, but there are also several bespoke Microsoft resource types:

* [Microsoft SQL Server](/admin/resources/datasources/microsoft-sql-server.md)
* [Microsoft SQL Server (Kerberos)](/admin/resources/datasources/microsoft-sql-server-kerberos.md)
* [Microsoft SQL Server (Azure AD)](/admin/resources/datasources/microsoft-sql-server-azure-ad.md)
* [Azure PostgreSQL](/admin/resources/datasources/azure-postgresql.md)
* [Azure Database for MySQL](/admin/resources/datasources/azure-mysql.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.strongdm.com/admin/deployment/integrations/microsoft.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.