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

# Microsoft application connectors

The .NET/PowerShell connectors — what they are, how they install, and which applications they integrate with.

Most OpenIAM connectors are written in Java and run on Linux. The connectors in this section are different: they are built in **.NET and PowerShell**, run as a Windows service, and exchange requests with OpenIAM over RabbitMQ. Each one drives a PowerShell module or a REST API from that Windows host, which is what gives them their reach into the Microsoft world.

What puts a connector in this section is that technology, not the vendor — which is why SAP SuccessFactors is in the list below.

## How they install and run

These three pages apply to **every** connector in this section, so each connector page covers only what is specific to it and points here for the rest.

<table><thead><tr><th width="296">Page</th><th>What it covers</th></tr></thead><tbody><tr><td><a href="/connector-configuration/microsoft/1-powershellconnectorinstallation.md">Installing PowerShell connectors</a></td><td>Requirements, the installer, running several connectors on one host, removing one, and the RabbitMQ queue type</td></tr><tr><td><a href="/connector-configuration/microsoft/2-powershellconnectorsusage.md">Using PowerShell connectors</a></td><td><code>Connector.config</code>, warm runner pools, hardening, logs, simulation mode and checking the installed version</td></tr><tr><td><a href="/connector-configuration/microsoft/3-powershellconnectorupdate.md">Updating PowerShell connectors</a></td><td>Moving to a newer connector version, including when the scripts have been customized</td></tr></tbody></table>

## The connectors

<table><thead><tr><th width="251">Connector</th><th>What it manages</th></tr></thead><tbody><tr><td><a href="/connector-configuration/microsoft/4-adpowershell.md">Active Directory</a></td><td>AD users, groups and their memberships</td></tr><tr><td><a href="/connector-configuration/microsoft/14-psgraph.md">Microsoft Graph PowerShell</a></td><td>Entra ID users, groups, licences and guest invitations, through Microsoft Graph</td></tr><tr><td><a href="/connector-configuration/microsoft/5-azuread.md">Entra ID / O365</a></td><td><strong>Deprecated</strong> — use the Microsoft Graph PowerShell connector instead</td></tr><tr><td><a href="/connector-configuration/microsoft/6-exchange.md">Exchange</a></td><td>Mailboxes — user, room, equipment and shared — and distribution group membership, on premises, online or hybrid</td></tr><tr><td><a href="/connector-configuration/microsoft/16-teams.md">Microsoft Teams</a></td><td>Phone numbers and voice settings on Teams users and resource accounts that already exist</td></tr><tr><td><a href="/connector-configuration/microsoft/9-sqlserver.md">Microsoft SQL Server</a></td><td>Server logins, database users and role membership</td></tr><tr><td><a href="/connector-configuration/microsoft/10-winlocal.md">WinLocal</a></td><td>Local users and groups on Windows machines that are <strong>not</strong> domain-joined</td></tr><tr><td><a href="/connector-configuration/microsoft/7-azuredevops.md">Azure DevOps</a></td><td>Users, groups and group memberships, read into OpenIAM</td></tr><tr><td><a href="/connector-configuration/microsoft/8-dynamics365.md">Dynamics 365</a></td><td>System users and contacts, with team and queue membership</td></tr><tr><td><a href="/connector-configuration/microsoft/12-dynamics365fo.md">Dynamics 365 Finance &#x26; Operations</a></td><td>System users and security roles</td></tr><tr><td><a href="/connector-configuration/microsoft/13-successfactors.md">SAP SuccessFactors</a></td><td>SuccessFactors users — the one non-Microsoft application in this family</td></tr></tbody></table>

{% hint style="info" %}
Entra ID was previously known as Azure AD.
{% endhint %}

## Also in this section

* [Building a custom PowerShell connector](/connector-configuration/microsoft/15-powershell-generic.md) — the **Generic** connector, shipped as a template for integrating an application that has no connector of its own.
* [AD Password Filter](/connector-configuration/microsoft/12-windowspasswordfilter.md) — **not a connector.** A standalone module that runs on a domain controller, catches password changes as they happen, checks them against OpenIAM's password policies and forwards the new password to the systems linked to that identity.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/connector-configuration/microsoft.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.