Single sign-on with Entra ID
Sign in with the corporate account, no second set of credentials. Deactivated accounts lose access automatically.
Integrations
Door James in the Microsoft 365 ecosystem
Sign-in, directory, calendar and chat: Door James builds on Microsoft 365 at four points instead of creating a parallel world.
In short
Door James integrates with Microsoft 365 at four points: single sign-on through Entra ID using OpenID Connect, profile and group synchronization through Microsoft Graph, bidirectional room calendar synchronization with Exchange Online, and a Teams app for bookings and notifications inside your tenant.
- Sign-in
- Entra ID through OpenID Connect
- Directory
- Microsoft Graph for profiles and groups
- Calendar
- Exchange Online, bidirectional
- Chat
- Teams app and notifications
Features
Groups drive permissions
Group memberships from Entra ID map onto area access, whitelists and roles.
Profile synchronization
Name, email address and profile data come from the directory instead of being maintained separately.
Outlook room calendars
Free/busy status is read and Door James bookings are written back.
Teams app
Delivered as a package for your tenant, with SSO through the Microsoft identity and an activity tab.
App registrations
Separate registrations for the components, each with the minimum permissions required.
Four touchpoints, one tenant
The Microsoft integration is deliberately modular: you can start with single sign-on and add calendar and Teams later. Each point has its own value and its own prerequisites.
The entry point is almost always Entra ID. It largely removes user management from Door James, and your offboarding process takes effect automatically. The second step is typically Exchange Online, because room calendars live there and double bookings cause the most friction. Teams follows when Door James should be present in daily work without people opening another application. Graph cuts across all of it and supplies profile data and groups.
What your IT has to do
The effort sits almost entirely on the permissions side, not on infrastructure: app registration, consent for the Graph permissions, release of the room resources, deployment of the Teams app. No inbound network ports, no agents and no server installations are required.
How it works
- 1
Create the app registration
Your IT registers Door James in Entra ID and grants the required Graph permissions.
- 2
Map groups and domains
Permitted domains, groups and roles are mapped to locations and areas in the Admin Panel.
- 3
Enable calendar and Teams
Room resources are linked and the Teams app is deployed in the tenant.
Frequently asked questions
Which Graph permissions are needed?
Read access to user information and groups for sign-in and profile data; read and write access to the relevant room calendars for room booking. We agree the concrete list with your IT during the rollout and keep it to the minimum.
Does our Exchange have to be in the cloud?
For calendar functions through Microsoft Graph a mailbox or resource in the Microsoft cloud is required. Pure on-premise Exchange scenarios are assessed case by case.
Does Door James work without Microsoft 365?
Yes. Microsoft is the most common case but not a requirement. Door James speaks OpenID Connect generically; Google is preconfigured as well.
Bring your actual setup to the call
Which tenant, which directory, which calendars, which identity provider. Thirty minutes is enough to say whether it fits – and where it will not.