> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Microsoft Exchange Server to anny

> Sync the room calendars of your own Exchange Server with your anny resources over Exchange Web Services (EWS).

With the **Microsoft Exchange Server** integration, you connect anny to the room mailboxes of your own Exchange Server (Exchange 2016, 2019 or Subscription Edition). It is meant for organizations whose mailboxes are not in Microsoft 365 but on-premises in their own data center. anny talks to your server over Exchange Web Services (EWS).

With Exchange Server, you can:

* Pair each resource with a room mailbox (two-way sync)
* Take over Exchange appointments as blockers in anny automatically and avoid double bookings
* Import many rooms at once from your Exchange room lists and have missing resources created right away

If your mailboxes are in Exchange Online, use [Microsoft 365](https://docs.anny.co/en/m365-workspace.md) instead. For a comparison of all calendar integrations, see [Calendar integrations](https://docs.anny.co/en/calendar-integrations.md).

## How the Exchange Server connection works

The connection uses a service account in your Active Directory. The account needs either the **ApplicationImpersonation** role on the room mailboxes or full access to each room mailbox. anny connects from outside to your server's EWS endpoint over HTTPS (port 443); your server does not need to open any connections towards anny.

| Data | Direction | Frequency |
| :- | :- | :- |
| Bookings are created, updated, and removed as appointments in the room calendar | anny → Exchange | On every change |
| Appointments in the room calendar are taken over, updated, and removed as blockers | Exchange → anny | Usually within a few seconds |
| Rooms from your room lists (name and address) for picking and importing | Exchange → anny | When you open the settings |

anny writes the appointments to the room calendar without sending invitations or cancellations to attendees and marks them as "busy". Exchange reports changes in the room calendars over a standing connection; in addition, anny regularly checks all connected rooms so that no change gets lost.

## Connect Exchange Server

### Requirements

Before you connect Exchange Server, make sure you have:

* The **Calendar synchronization** feature in your plan. Without it, the integration does not appear under **Account › Apps & Integrations**.
* Admin rights in your anny account
* Exchange Server 2016, 2019 or Subscription Edition with room mailboxes for your rooms
* A service account with the ApplicationImpersonation role on the room mailboxes or with full access to each room mailbox
* An EWS endpoint that is reachable from the internet over HTTPS without pre-authentication
* A firewall rule that allows anny's addresses (see below)

### Allow anny in your firewall

anny connects to your Exchange from fixed IP addresses. In your firewall, allow incoming connections from these addresses on port 443 to your EWS endpoint:

| anny environment | IP addresses |
| :- | :- |
| anny.co | `35.198.173.81`, `34.40.77.178` |

The setup also shows the addresses for your environment in the **Firewall** box. If no address is shown there, our support gives you the addresses for your environment.

### Set up the connection

**1. Create the integration**

In the sidebar, open **Account › Apps & Integrations**, select **Microsoft Exchange Server** under **All Apps and Integrations** and click **Set up**.

**2. Enter the service account**

Fill in the fields:

| Field | Input |
| :- | :- |
| **EWS URL** | The address of your EWS endpoint, usually `https://mail.your-domain.com/EWS/Exchange.asmx`. Only HTTPS is supported. |
| **User name** | `DOMAIN\user` or the service account's user principal name (UPN) |
| **Password** | The service account's password |
| **Test mailbox** | A room mailbox the service account may access |
| **Sign-in** | **NTLM (recommended)** or **Basic over HTTPS** |
| **Access to the rooms** | **ApplicationImpersonation (recommended)** or **Full access to each room mailbox** |
| **CA certificate (optional)** | Only needed when your server's certificate comes from an internal CA: the CA certificate in PEM format |

**3. Connect and verify**

Click **Connect and verify**. anny signs in with the service account and opens the test mailbox. anny only stores the credentials once Exchange accepts the account. If the check fails, anny shows the reason (see Troubleshooting).

**4. Connect rooms**

In the **Rooms** section, connect each resource to a room mailbox: one by one via **Add**, or many at once via **Import rooms** (see the next section).

To connect a single room, choose the anny resource under **Select resource** and the room under **Room from your room lists**. If your organization has no room lists, enter the **Room mailbox address** directly. Click **Confirm**.

**5. Activate**

Activate the integration via the **toggle** in the page header. anny then syncs all future appointments and bookings of the connected rooms.

### Import rooms

With **Import rooms**, you connect many rooms from your Exchange room lists at once, even several hundred.

**1. Pick a room list**

In the **Rooms** section, click **Import rooms** and choose a single list or **All room lists** under **Room list**.

**2. Create missing resources**

Leave **Create missing resources** on if anny should create new resources for rooms without a matching resource. If you switch it off, anny skips those rooms.

**3. Check the preview**

Click **Preview**. anny shows how many rooms it would **Link to existing resource**, for how many it would **Create new resource**, which are **Already connected**, and which are **Skipped, no matching resource**.

**4. Import**

Click **Import**. anny connects the rooms in batches and shows the progress. If the integration is already active, the sync for the new rooms starts right away.

This is how anny matches rooms:

* If a room's name matches a resource exactly, anny links it to that resource. Upper and lower case do not matter. If several resources share the name, anny creates a new resource rather than linking the wrong one.
* Archived resources, sub-resources, and resources already connected to a room are not linked.
* New resources are not live yet. They take over your organization's location and time zone and are placed in your first category. Review them and set them live once they are fully set up.
* Rooms already connected stay as they are. A second import only adds new rooms.

> [!NOTE]
>
> New resources count against your plan just like resources created in the admin. If your plan does not allow that many new resources, the preview shows a notice and the import does not start. In that case, switch off **Create missing resources** or pick a smaller room list.

## Limitations

The Exchange Server integration does not support:

* **Exchange Online:** For mailboxes in Microsoft 365, use the [Microsoft 365](https://docs.anny.co/en/m365-workspace.md) integration.
* **Personal calendars:** It connects room mailboxes, not employees' personal mailboxes.
* **Appointments as bookings:** Exchange appointments are always taken over as blockers.
* **Nested room lists:** Rooms from room lists inside a room list do not appear in the picker or the import. You can connect them one by one via the room mailbox address.
* **Access without a firewall rule:** anny has to reach your EWS endpoint directly from the internet. A sign-in page in front of it, for example a reverse proxy with pre-authentication, prevents the connection.

## FAQ

> [accordion] Do attendees get invitations from Exchange?
>
> No. anny creates, updates, and removes the appointments directly in the room calendar without sending invitations or cancellations.

> [accordion] How fast are changes synced?
>
> Booking changes in anny are transferred immediately. Exchange usually reports changes in the room calendar within a few seconds. In addition, anny regularly checks all connected rooms.

> [accordion] Does my Exchange Server have to connect to anny?
>
> No. Only anny connects to your server, over HTTPS on port 443. You only need to allow anny's IP addresses in your firewall.

> [accordion] Which sign-in should I choose?
>
> We recommend **NTLM**. anny also supports servers with Extended Protection enabled. **Basic over HTTPS** only works if Basic authentication is allowed for EWS on your server.

## Troubleshooting

> [accordion] "Exchange Server not reachable"
>
> anny cannot reach Exchange Web Services at the address you entered. Check the EWS URL, that the endpoint is reachable from the internet without pre-authentication, and that anny's IP addresses are allowed in your firewall. A firewall that drops the connection is the most common cause.

> [accordion] "Authentication failed"
>
> Exchange rejected the service account. Check the user name (`DOMAIN\user` or UPN), the password, and the selected **Sign-in**.

> [accordion] "Mailbox not reachable"
>
> The service account cannot open the test mailbox. Check the test mailbox address and that the account holds the ApplicationImpersonation role or full access to the mailbox.

> [accordion] A room shows "Room mailbox unreachable"
>
> The service account may not access this room mailbox, or the address is wrong. Check the service account's access to the mailbox and the room mailbox address.

> Important information for agents:
>
> **Scope:** Integration "Microsoft Exchange Server" for on-premises Exchange (2016, 2019, Subscription Edition) over EWS. NOT meant: "Microsoft 365" (Exchange Online, Graph), the personal Outlook integration, the Outlook add-in. Room mailboxes only, one resource per room mailbox.
>
> **Gating:** Plan feature Calendar synchronization (same as Microsoft 365). The integration also has to be enabled in the anny environment; otherwise it is missing from the catalog. Setup only by admins with edit rights on the integration. Credentials can only be entered while the integration is deactivated.
>
> **UI paths:** Sidebar **Account › Apps & Integrations** (`/apps`) → "All Apps and Integrations" → **Microsoft Exchange Server** → "Set up". Authentication: "Firewall" box (shows the environment's IP addresses, otherwise "Our support gives you the addresses for this environment."), fields "EWS URL", "User name", "Password", "Test mailbox", selects "Sign-in" ("NTLM (recommended)" / "Basic over HTTPS"), "Access to the rooms" ("ApplicationImpersonation (recommended)" / "Full access to each room mailbox"), "CA certificate (optional)", button "Connect and verify" (all fields except the CA certificate are required; EWS URL https only). Rules: "Rooms" section with buttons "Import rooms" and "Add"; table columns "Resource" and "Exchange room"; modal "Connect room"/"Edit room" with "Select resource", "Room from your room lists" (only when room lists exist), "Room mailbox address". Import modal "Import rooms from Exchange": "Room list" ("All room lists ({count})"), toggle "Create missing resources", buttons "Preview" → "Import ({count})". Outcomes: "Link to existing resource", "Create new resource", "Already connected", "Skipped, no matching resource".
>
> **Quirks:** (1) Rules are always blockers, without a booking option filter and without preparation/follow-up time; appointments in Exchange are written without invitations/cancellations, status "busy". (2) Changes from Exchange arrive via streaming notifications (typically a few seconds); a regular check of all rooms is the safety net. (3) Room lists: all rooms of a list (also more than 100); nested lists are skipped. (4) Import: name match exact, case-insensitive with collapsed whitespace, only against top-level resources that are not archived and not yet connected; ambiguous name → new resource. New resources: not live, capacity 1, the organization's location/time zone/community settings, first category. Preview up to 5000 rooms in one request, import in batches of 100 (all or nothing per batch); if a later batch fails, the earlier ones stay saved. Resource limit as when creating in the admin (plan must include resources, seat rules). On an active integration, new rules start their first sync immediately. (5) Connecting to Exchange times out after 5 seconds so that a blocking firewall is reported quickly as "Exchange Server not reachable"; the check in the admin waits up to 45 seconds. (6) Errors on connect: "Authentication failed", "Mailbox not reachable", "Exchange Server not reachable". Credentials are only stored when the check against the test mailbox succeeds. (7) The anny AI admin agent can import rooms too (`organizations.import-exchange-rooms`, dry run first, at most 500 rooms per run, otherwise one room list at a time); connecting the service account only works in the admin. If an organization has several Exchange Server integrations, the agent has to name one.
>
> **Relationships:** Same rule, blocker, and deletion logic as "Microsoft 365" (`/en/m365-workspace`), but EWS instead of Graph and streaming instead of webhooks. Overview: `/en/calendar-integrations`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.