Overview
This guide walks Azure/Entra ID administrators through integrating Jiminny with your Office 365 environment. By following these steps, you'll enable key Jiminny features, including calendar sync, email sync, Teams integration, and Microsoft sign-in, while maintaining full control over what data Jiminny can access.
This is a hub article designed to orient you and guide you to the right next steps. It does not repeat detailed instructions from task-specific articles; instead, we link to those as needed.
Who this is for: Microsoft Entra ID administrators (Global Administrator, Cloud Application Administrator, or Application Administrator) managing Jiminny deployment in your organization.
What You'll Need
Before you start, confirm you have:
Global Administrator, Cloud Application Administrator, or Application Administrator role in Microsoft Entra ID (required to grant consent for the Jiminny application)
Active Office 365 subscription (any tier - non Personal Accounts)
Jiminny account provisioned and ready to use (your Jiminny Account Manager will confirm this with you)
How the Integration Works
The Multi-Tenant Application Model
Jiminny is registered as a multi-tenant application in Microsoft's application ecosystem. This means:
Jiminny exists as a single app registration in Jiminny's tenant
When you grant consent, a service principal is created in your tenant
This service principal is what manages all Jiminny permissions and data access within your organization
Delegated Permissions Only
All permissions requested by Jiminny are delegated permissions. This is important:
Jiminny never accesses your data directly or independently
Data is accessed only on behalf of signed-in Jiminny users
A user's Jiminny experience is limited by their own Office 365 permissions
If a user can't access a calendar in Outlook, they can't see it in Jiminny either
Scopes Are Feature-Specific
Not all permission scopes are required. Jiminny requests scopes based on the features your organization uses:
Authentication/SSO – enables Microsoft sign-in
Calendar Sync – enables calendar event sync and Notetaker integration
Teams – enables sharing clips to Teams and receiving Team notifications
Email Sync – enables email message syncing (requires additional setup)
If your team only uses Jiminny for recording and sharing, you may not need all scopes. The consent flow will show exactly which scopes are being requested.
Setup Steps
Step 1: Grant Consent for Office 365 Integration
Start by granting consent for the Jiminny application. This creates the service principal in your tenant and enables the integration.
This article walks you through the consent flow in Microsoft Entra ID.
Step 2: Enable Email Sync (If Your Team Needs It)
If your organization wants to sync emails to Jiminny, make sure you selected "Grant access to Mailbox" or "Grant access to all recommended resources" in Step 1, which includes the Mail.Read permission. Once consent is granted, each user enables email sync in their Jiminny profile. For details on what gets synced, how filtering works, and how data is handled:
(Skip this step if your team doesn't need email syncing.)
Step 3: Verify the Integration is Working
Once consent is granted, test that the integration is live:
Users can sign in (or register) with Microsoft – Users should see a "Sign in with Microsoft" option on the Jiminny login page
Calendar events appear – If you've enabled calendar sync, users should see their Outlook calendars and events in Jiminny
Emails are syncing – If you've enabled email sync, check that recent emails from relevant mailboxes are appearing in Jiminny
If any of these aren't working, see the Need Help? section below.
Permissions Overview
Here's a summary of the permission categories Jiminny may request, depending on which features your organization uses:
Permission Category | What Jiminny Can Do | Required? |
Authentication | Sign in users via Microsoft Entra ID, read basic profile (name, email) | Always required |
Calendar | Read and update calendar events; read online meeting details | Required if using Automatic Notetaker or Calendar Sync |
Teams | Read team/channel info; send messages to channels and chats on behalf of users | Only if using Teams sharing |
Read email messages (read-only, cannot send, modify, or delete) | Only if using Email Sync |
For a complete technical breakdown of each scope and how it's used, see the full reference:
Need Help?
Login or consent issues after setup? → Troubleshooting Office 365 Login and Consent Issues
Other questions or issues? Contact Jiminny support directly, and our team will help you troubleshoot or answer questions about your Office 365 integration.
Note: Microsoft rebranded "Azure Active Directory" to "Microsoft Entra ID" in mid-2023. You may see both names in older documentation or in the Azure portal, but they refer to the same service.