Before You Troubleshoot
Before working through specific errors, verify these prerequisites:
Consent has been granted - An administrator has completed the consent flow. See Grant Consent for Office 365 Integration with Jiminny for instructions.
User is assigned (if required) - If "Assignment required?" is enabled, the user must be added to the Jiminny enterprise application in Entra. See "User is not assigned to a role" section below.
Correct tenant - You are signing in with an account from the correct Microsoft Entra ID tenant.
Browser compatibility - You're using a supported browser (Chrome, Edge, Safari, Firefox). Clear cache and cookies before troubleshooting.
Error: "The signed-in user EmailHidden is not assigned to a role for the application"
What this means: The Jiminny service principal requires explicit user assignment, but your account hasn't been added yet.
Root cause: In the Jiminny enterprise application properties, the setting "Assignment required?" is set to Yes, which restricts access to only assigned users and groups.
Solution:
Your Microsoft Entra ID administrator should take one of these actions:
Option A: Assign the user directly (recommended for small teams)
Navigate to Identity > Applications > Enterprise applications
Search for and select Jiminny
Select Users and groups from the left menu
Click Add user/group
Select the user(s) or group(s) who need access
Click Assign
Option B: Remove the assignment requirement (recommended for larger organizations)
Navigate to Identity > Applications > Enterprise applications
Search for and select Jiminny
Select Properties from the left menu
Set Assignment required? to No
Click Save
Once this is configured, the user should be able to log in to Jiminny.
Error: "Need admin approval" or "AADSTS65001: The user or administrator has not consented to use the application"
What this means: Your Microsoft Entra tenant's consent policy requires administrator approval before users can access Jiminny. This approval hasn't been granted yet.
Root cause: Your organization's Entra ID is configured to require admin consent for third-party applications. This is a security best practice in many organizations.
Solution:
Your Microsoft Entra ID administrator should:
Option A: Grant tenant-wide consent (one-time setup)
Follow the pre-authorization flow in Grant Consent for Office 365 Integration with Jiminny
This grants consent for all users in the tenant and prevents users from being prompted individually
Option B: Approve pending consent requests
Navigate to Identity > Applications > Enterprise applications
Select Admin consent requests from the left menu (if available)
Find the request from Jiminny
Review the permissions being requested
Click Review permissions and consent
Click Accept
Once consent is granted, users will be able to sign in to Jiminny.
Error: "The provider denied the request. Please try again"
What this means: Something prevented the Microsoft identity platform from completing the authentication request. This is usually temporary or session-related.
Root causes:
Stale browser session or cached authentication tokens
Temporary issue with the Microsoft identity platform
Cookies or session data from a previous failed attempt
Solution:
Clear your browser cache and cookies:
Chrome: Press
Ctrl+Shift+Delete(Windows) orCmd+Shift+Delete(Mac) > Select "All time" > Check "Cookies and other site data" and "Cached images and files" > Click Clear dataEdge: Press
Ctrl+Shift+Delete> Select "All time" > Check "Cookies and other site data" and "Cached images and files" > Click Clear nowSafari: Go to Safari > Settings > Privacy > Click Manage Website Data > Select all > Click Remove
Try signing in again from a private/incognito window:
Chrome/Edge: Press
Ctrl+Shift+N(Windows) orCmd+Shift+N(Mac)Safari: Press
Cmd+Shift+NFirefox: Press
Ctrl+Shift+P(Windows) orCmd+Shift+P(Mac)
If the error persists, try a different browser (to rule out browser-specific issues)
If the error continues:
Contact your Microsoft Entra ID administrator to verify:
The Jiminny service principal exists in Enterprise applications
Consent has been granted (check Permissions under the Jiminny application)
The user's account is active and licensed for Office 365
Error: Jiminny doesn't appear in Enterprise Applications
What this means: The Jiminny service principal hasn't been created in your Entra ID tenant yet.
Root cause: Service principals are only created when an admin grants consent for the first time. If consent has never been granted, Jiminny won't appear in Enterprise applications.
Solution:
An administrator must complete the consent flow:
Follow the full setup in Grant Consent for Office 365 Integration with Jiminny
The Jiminny service principal will be created automatically during the consent process
After consent is granted, you can assign users or groups as needed
This is a required step before any user can sign in with Office 365.
Error: Consent was granted, but users still can't log in
What this means: Consent is complete, but something else is preventing access.
Troubleshooting checklist:
Check assignment settings: Go to Enterprise applications > Jiminny > Properties. If "Assignment required?" is Yes, the user must be added to Users and groups.
Verify permissions were granted: Go to Enterprise applications > Jiminny > Permissions. You should see the expected Microsoft Graph delegated permissions listed (e.g., Calendars.ReadWrite, Mail.Read). See Technical Details for the full list.
Check user group membership: If using group-based assignment, verify the user is a member of the assigned group in Entra ID.
Clear browser cache: Follow the cache-clearing steps in the "The provider denied the request" section above.
Try a private/incognito window: This rules out cached authentication issues.
Try a different device or browser: This confirms the issue isn't device-specific.
If the user still cannot log in after checking all of these, contact Jiminny support with the details below.
Error: Email sync not working after Office 365 login
What this means: The user successfully signed in to Jiminny, but emails are not syncing from Office 365.
Root causes:
The Mail.Read permission wasn't granted during the consent process
Email import hasn't been enabled in the user's Jiminny profile settings
Solution:
Step 1: Verify the Mail.Read permission was granted
Navigate to Identity > Applications > Enterprise applications
Search for and select Jiminny
Select Permissions from the left menu
Look for "Mail.Read" in the list of granted permissions
If missing, the administrator should re-grant consent. See Grant Consent for Office 365 Integration with Jiminny
Step 2: Enable email import in Jiminny
In Jiminny, go to your profile settings
Navigate to Integrations
Find Import Email Conversations
Toggle the setting to On
Email conversations should begin syncing within a few minutes.
General Troubleshooting Steps
If you encounter any Office 365 login issue, try these steps in order:
Clear browser cache and cookies (detailed instructions in the "The provider denied the request" section above)
Try an incognito/private window -This bypasses cached data and extensions
Try a different browser -This rules out browser-specific issues
Sign out completely and sign back in -Close all Jiminny tabs, clear cache, then start fresh
These steps resolve most temporary authentication issues.
Still Need Help?
If you've worked through the troubleshooting steps above and still need assistance:
Gather information:
The exact error message you're seeing
A screenshot of the error
Your Microsoft Entra ID tenant name
Whether this affects one user or multiple users
Contact Jiminny support:
Use the help widget in your Jiminny account
Email: support@jiminny.com
Provide the information from step 1
For Microsoft-specific questions: