Skip to main content
A Global Administrator has to approve the connection. For sign-in data, such as login locations, sign-in status, and success and failure counts, the tenant also needs a Microsoft Entra ID P1 license, which includes the audit logs Telivy reads. Without P1, Telivy still shows accounts, MFA status, and Secure Score.Microsoft lists the plans and prices on its Entra pricing page.
The first sync can take from 15 minutes to a few hours, depending on the number of users and how much history the tenant has.If there is still nothing after an hour, go to Setup > Connect Cloud, open the actions menu on the Microsoft 365 card, and select Refetch now. If the card says the connection needs attention, select Reconnect Microsoft 365 and approve again. You get an email when the Microsoft 365 data is ready.
Each icon (Microsoft Entra ID, Exchange, SharePoint, OneDrive, and Policy management) stands for a set of permissions. A grey icon means the tenant has not granted that permission yet. Select it to open Microsoft’s consent screen. See Microsoft 365 Security.
Telivy checks every few hours that each Microsoft 365 connection still works. When Microsoft refuses to renew Telivy’s access, the assessment is marked as needing a reconnect and you get an email saying why. Most causes are changes inside the client’s own tenant, so reconnecting only works once that change is undone or accounted for.The reasons you may see:
  • Access was revoked. Someone changed or reset the password of the admin account that connected Telivy, or removed the permissions it granted. Reconnect from Setup > Connect Cloud.
  • The connection was inactive for too long. The tenant’s sign-in policy ended the session. Reconnect.
  • The connecting admin account was removed or its credential expired. Reconnect with an admin account that is still active in the tenant.
  • The Telivy app was disabled or removed in the tenant. An administrator turned off or deleted the Telivy enterprise application. To turn it back on, open the Microsoft Entra admin center, go to Enterprise applications > Telivy > Properties, set “Enabled for users to sign in?” to Yes, and reconnect. If the app was deleted, reconnecting adds it again.
  • The tenant no longer exists. Microsoft reports the tenant as not found, which happens when it was deleted or has no active subscription left. If the client moved to a new tenant, reconnect with an admin account from the new one. If the client no longer uses Microsoft 365, leave the connection as it is.
Until the connection is restored, the client’s Microsoft 365 findings stay as they were at the last successful check.
Nobody can sign in to a disabled account, so Telivy does not judge its MFA. Disabled accounts show N/A in MFA Status and are not counted in Accounts without MFA.
Telivy now turns every Secure Score control the tenant still needs to act on into a Cloud finding with a severity, a score impact, and remediation steps. They appear under Risk Insights on the Cloud tab and on the assessment’s Risk tab. See Secure Score controls as findings.
Microsoft calculates the score from the controls that apply to each tenant, so licensing, the services in use, third-party security tools, tenant size, and user behavior all change it. Understanding Microsoft Secure Score explains each factor.
No. External B2B guest accounts, the ones with #EXT# in their user name, are never counted as billable users. Account > Usage shows them in their own M365 guests column so you can see why the billed user count is lower than the tenant’s total.
Google Workspace is blocking the access Telivy asks for. There are two common causes.API access is restricted. To allow it:
  1. Sign in to the Google Admin console.
  2. Go to Security > API Controls > Manage Google Services.
  3. Find Google Workspace Admin and select Change Access.
  4. Select Unrestricted: Any user-approved app can access a service.
A service is disabled. To turn it on:
  1. Sign in to the Google Admin console.
  2. Go to Security > API Permissions.
  3. Enable any disabled services.
Google’s community thread on this error has more detail.
On the Cloud tab, open Google Workspace and select Show No MFA on the Accounts Status table. It lists only the accounts where MFA is Not Enforced. See Google Workspace Security.