> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetjamie.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Exchange Server (EWS)
> Connect an on-premises Exchange calendar to Jamie.
If your organization runs its own Exchange Server, or has a hybrid setup where mailboxes have not been migrated to Exchange Online, the regular [Outlook integration](/getting-started/calendar/outlook) cannot reach your calendar. Jamie connects to these mailboxes through **Exchange Web Services (EWS)** instead, and you get the same calendar features: upcoming meetings in Jamie, automatic meeting titles, and speaker name suggestions from the invitee list.
Exchange Server (EWS) is available on the **Enterprise plan** and is enabled per workspace by Jamie. Request access from **Settings → Integrations → Exchange Server (EWS)** and our team will contact you about setup.
## Is this the right integration for you?
You need Exchange Server (EWS) when connecting Outlook fails with:
> "Resource not found: The mailbox is either inactive, soft-deleted, or is hosted on-premise."
Jamie's Outlook integration uses the Microsoft Graph API, which only serves mailboxes hosted in Exchange Online (Microsoft 365). When your mailbox lives on an on-premises Exchange Server, Graph cannot see it. Jamie shows an **Exchange Server** card in that case with a link to request access.
If your mailbox is in Exchange Online, use the [Outlook integration](/getting-started/calendar/outlook) instead; it needs no setup on your organization's side.
## How it works
* **Read-only calendar access.** Jamie reads your Exchange calendar over EWS. It never creates, edits, or deletes events on your Exchange Server, and it does not read your inbox or address book.
* **Two credential modes.** Your organization chooses one during onboarding:
| Mode | How it works |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| **Personal credentials** | Each user enters their own Exchange password in Jamie. Exchange applies the user's existing mailbox permissions. |
| **Service account** | Jamie configures a service account supplied by your Exchange admin. Users never enter a password. |
* **Encrypted credentials.** Saved credentials are encrypted at rest. Personal passwords are never shown to workspace administrators.
* **Change notifications.** Your Exchange Server pushes calendar changes to Jamie over HTTPS, so new and updated meetings show up quickly. Jamie also reconciles calendars on a schedule.
* **Compatibility.** Jamie speaks the Exchange 2013 SP1 EWS schema, which covers Exchange Server 2013 SP1, 2016, and 2019. A 2013 legacy compatibility mode is available. **NTLM** (default), **Basic**, and **OAuth** (Microsoft Entra ID tokens through Hybrid Modern Authentication) are supported.
## What your Exchange administrator needs to provide
Jamie configures the connection with you during onboarding. Have the following ready:
| Item | Details |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **EWS endpoint URL** | Usually `https://mail.example.com/EWS/Exchange.asmx`. Jamie's EWS sync service must be able to reach it over HTTPS (port 443) with a valid TLS certificate, either from Jamie's static IP addresses or through a site-to-site VPN (see [Network access](#network-access)). If a reverse proxy or pre-authentication gateway fronts EWS, it must let Jamie's EWS requests through. |
| **Authentication scheme** | NTLM, Basic, or OAuth (Microsoft Entra ID tokens through Hybrid Modern Authentication). |
| **Credential mode** | Personal credentials, or a service account supplied by your Exchange admin that Jamie configures (see above). |
| **Network access** | Allowlist Jamie's static IP addresses on the firewall or gateway in front of EWS, or arrange a site-to-site VPN with Jamie (see [Network access](#network-access)). |
| **Outbound access to Jamie** | Allow the Exchange Server to make outbound HTTPS (port 443) requests to `api.meetjamie.ai` so it can deliver calendar change notifications. See [Firewall Ports](/enterprise/admins/firewall-ports) for the full list of Jamie endpoints. |
| **Matching email addresses** | Each user's Jamie account email must be the primary SMTP address of their Exchange mailbox. Jamie uses it to locate the mailbox and it cannot be changed from the Exchange settings page. |
## Network access
Jamie's EWS sync service runs in Google Cloud and connects to your Exchange Server from **dedicated static IP addresses**. Your network team can allowlist those addresses on the firewall, reverse proxy, or pre-authentication gateway in front of EWS, so the endpoint does not have to accept traffic from the whole internet. Jamie shares the current addresses with you during onboarding.
If your security policy does not allow EWS to be reachable from the internet at all, Jamie can instead set up a **site-to-site VPN** between its Google Cloud network and yours (Google Cloud VPN over IPsec). EWS traffic then stays on the private tunnel. This is planned together with your network team during onboarding.
In both setups, your Exchange Server still needs outbound HTTPS access to `api.meetjamie.ai` to deliver calendar change notifications.
## Setting it up
### 1. Request access
1. Click on your workspace name (top left corner)
2. Go to **Settings**
3. Navigate to **Integrations** > **Exchange Server (EWS)**
4. Click **Request access**
Our team will reach out to your workspace admin to plan the onboarding. If you tried Outlook first and saw the on-premise message, the same **Request access** button appears on the Outlook page.
If **Exchange Server (EWS)** is not listed under Integrations, the integration has not been enabled for your workspace yet. Contact support to get started.
### 2. Onboarding with Jamie
During onboarding, Jamie support configures the EWS endpoint, authentication scheme, compatibility version, and credential mode for your workspace, then enables sync. Until this is done, the Exchange Server page shows **Exchange is being configured**.
### 3. Connect your mailbox
With **personal credentials**:
1. Open **Settings** > **Integrations** > **Exchange Server (EWS)**
2. Click **Connect EWS**
3. Confirm your Jamie account email. Your Exchange mailbox must use this address.
4. Enter your Exchange password and click **Connect**
Your credentials are encrypted at rest and used only to access your Exchange calendar. The **Your Exchange mailbox** card shows **Synchronizing** while Jamie performs the first sync.
With a **service account**, there is nothing to enter. Jamie manages the connection, and the card shows your mailbox address with its sync status.
### 4. Choose your calendars
Once the first sync completes, the Exchange Server page lists the calendars in your mailbox. Select the ones you want in Jamie and click **Apply**. Jamie schedules those calendars to sync and removes events from any calendar you deselect.
## Permissions and data
| Jamie reads | Why |
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Event titles, times, descriptions, locations, and meeting links | Shows upcoming meetings, sets meeting titles automatically, and lets you join from Jamie |
| Organizer and invitee names and email addresses | Identifies meeting participants and suggests speaker names |
Jamie never creates, edits, or deletes events on your Exchange Server, and does not read your inbox or address book. With a service account, your Exchange admin controls which calendars the account can read. With personal credentials, Exchange applies your account's existing permissions; Jamie only uses the connection for calendar sync.
## Troubleshooting
| Message in Jamie | What it means | What to do |
| ------------------------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Exchange rejected the credentials** | Your Exchange password changed or expired, or the service account was locked | Personal credentials: click **Disconnect**, then **Connect EWS** with your current password. Service account: ask your workspace admin to coordinate with Jamie support. |
| **Exchange denied access to your calendar** | Exchange accepted the login but refused the calendar | Ask your Exchange admin to check the calendar permissions for your account or the service account. |
| **A valid Jamie account email is required** | Your Jamie account email is not a valid mailbox address | Contact support to update your account email. |
| **Exchange sync needs attention** | The EWS configuration for your workspace no longer works | Contact Jamie support to check the endpoint, authentication scheme, or compatibility version. |
| **A selected calendar is unavailable** | A calendar you selected was removed or renamed on Exchange | Deselect it and click **Apply**, or refresh the calendar list. |
| **Retrying sync** | The last sync attempt failed | No action needed. Jamie retries automatically. If it persists, check that your Exchange Server can reach `api.meetjamie.ai`. |
## FAQs
Jamie only syncs events that look like real meetings, so your upcoming list stays focused on what matters. An event is synced when it:
* Falls within roughly the next 10 days (Jamie keeps a rolling window of upcoming events)
* Has at least two participants (you plus at least one other person)
* Hasn't been declined by you
* Isn't an all-day or multi-day event (24 hours or longer)
Jamie automatically skips events that are usually personal time rather than meetings:
* All-day and multi-day events
* Events you've declined
* Solo events with no other participants (personal holds and time blocks)
* Events whose title looks like focus or availability time — for example "Focus time", "Focus block", "Do not disturb", "No meetings", "Out of office", or "Off work"
Recurring meetings are synced as individual occurrences within the window, and events you cancel or delete are removed from Jamie automatically.
With personal credentials, yes: Jamie needs it to authenticate against your Exchange Server. It is encrypted at rest, used only for calendar access, and never shown to workspace administrators. Click **Disconnect** at any time to remove it. With a service account, you never enter a password.
Once your mailbox is migrated, the regular [Outlook integration](/getting-started/calendar/outlook) works without any setup. Disconnect Exchange Server (EWS), then connect Outlook. If your whole organization is migrating, tell Jamie support so the EWS configuration can be retired.
Yes. Users whose mailboxes are already in Exchange Online connect through Outlook; users whose mailboxes are still on-premises connect through Exchange Server (EWS). Each user connects the integration that matches where their mailbox lives.