Viva Engage user provisioning issue – licensed user unable to complete Viva Engage access

Ila Parmar (SEC) 0 Reputation points
2026-10-15T02:44:55.32+00:00

We are experiencing a Viva Engage provisioning/access issue affecting one user. The user can successfully authenticate to Microsoft 365 and Viva Engage; however, when accessing Viva Engage directly, the following message is displayed:

“You've successfully signed in to Viva Engage, but it looks like your access hasn't been fully set up yet. Please contact your admin to complete your access setup.”

The user's Viva Engage Core service plan has been verified as enabled.

The issue is also affecting our SharePoint Online intranet. The Viva Engage Conversations web part fails for the affected user and displays:

“Sorry, something went wrong when loading conversations. Please try again.”

Troubleshooting/findings:

  • Microsoft 365 account is active.
  • Microsoft 365 licence is assigned.
  • Viva Engage Core service plan is enabled.
  • Microsoft 365/Viva Engage authentication succeeds.
  • Direct Viva Engage access does not complete successfully.
  • SharePoint/Vintranet itself loads successfully.
  • Viva Engage Conversations web part fails to load for the affected user.
  • Issue therefore reproduces independently of the SharePoint Conversations web part. How to fix this issue
Microsoft 365 and Office | Microsoft Viva | Viva Engage
0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Teddie Dang 1,625 Reputation points Independent Advisor
    2026-10-15T03:30:39.1733333+00:00

    Hi @Ila Parmar (SEC)

    This error message indicates that the user's Microsoft Entra ID account is authenticating successfully, but Viva Engage is unable to complete the user's access setup. Since the Viva Engage Core service plan is already enabled, the issue is more likely related to user provisioning or synchronization within the Viva Engage service than to licensing itself.

    You can try the following steps:

    1.Check whether the user exists in the Viva Engage network:

    • Go to engage.cloud.microsoft and open the Admin Center (Gear icon).
    • Navigate to Data management under Governance and compliance.
    • Export the user list.
    • Open the exported CSV file and search for the affected user's email address or UPN.

    2.Attempt reprovisioning

    • In the Microsoft 365 admin center, open the affected user and select Licenses and apps.
    • Untick the Viva Engage Core service plan and save the change.
    • Wait 15-30 minutes.
    • Re-enable the service plan and save.
    • Have the user sign out completely and then sign in again using an InPrivate/Incognito browser window.

    If that does not help, you can try reprovisioning by removing and reassigning the entire Microsoft 365 license:

    • Remove the user's Microsoft 365 license.
    • Wait approximately 30-60 minutes.
    • Reassign the license.
    • Have the user sign in again using a fresh InPrivate/Incognito session.

    Because the issue occurs both in Viva Engage directly and in the Viva Engage Conversations web part, the evidence suggests an issue with the user's Viva Engage access setup rather than with SharePoint itself.

    If the issue persists after reprovisioning, I recommend opening a support request with Microsoft Support and providing the user's UPN, screenshots of the error messages, and confirmation that the account is active and the Viva Engage Core service plan is enabled. Microsoft can then investigate the user's backend provisioning status.

    Was this answer helpful?

  2. AI answer

    2026-10-15T02:45:20.1933333+00:00

    For this symptom, the most likely gap is that the user can authenticate, but the Viva Engage account is not fully matched to a Microsoft 365 identity or the tenant is enforcing Microsoft 365 identity/licensing requirements and the user is not fully provisioned in that path.

    Use this admin checklist:

    1. Confirm the user exists in both Viva Engage and Microsoft 365 / Microsoft Entra ID
      • In the Viva Engage admin center, export users from the data export page.
      • Compare that user list with Microsoft 365 / Microsoft Entra ID.
      • If the user exists in Viva Engage but not correctly matched in Microsoft 365 / Microsoft Entra ID, create or correct the Microsoft 365 identity mapping.
      • Microsoft states that when Microsoft 365 identity is enforced, any user without the corresponding Microsoft 365 identity is locked out of Viva Engage.
    2. Audit the user’s Microsoft 365 identity match with the PowerShell audit process
      • Use the Microsoft Entra ID module for Windows PowerShell.
      • Run the UserMatchToAzureAD.ps1 process against the users exported from Viva Engage.
      • Review the output CSV and check whether the affected user shows exists_in_azure_ad as FALSE.
      • If so, either create the user in Microsoft 365 / Microsoft Entra ID or suspend the stale Viva Engage account if it should not exist.
      • After correction, run the audit again to confirm the user is now found.
    3. Check whether Microsoft 365 identity enforcement / license enforcement is enabled
      • If enforcement is enabled, each Viva Engage user must have:
        • a Microsoft 365 license, and
        • Viva Engage Core or Yammer Enterprise.
      • This enforcement is irreversible.
      • A user can sign in successfully but still be blocked from full access if the identity/license enforcement requirements are not fully satisfied.
    4. Verify the service plan assignment at the user level
      • Since the Viva Engage Core service plan was already checked, verify that it is actually applied to the affected user and not only enabled in the parent license configuration.
      • Microsoft notes that bundled Microsoft 365 plans include Viva Engage Core, but access depends on the service plan being assigned to the user.
      • PowerShell can be used to identify unlicensed users with: 
             Get-MsolUser -All -UnlicensedUsersOnly
      • PowerShell can also be used to manage or reapply the Viva Engage Core service plan.
    5. If using Teams or embedded experiences, verify Viva Engage sign-in is enabled in Microsoft Entra ID
      • In Microsoft Entra admin center, go to Identity > Applications > Enterprise Applications > Viva Engage > Properties.
      • Ensure Enabled for users to sign-in? is set to Yes.
      • Also ensure the tenant does not block Viva Engage URLs and IPs.
    6. Retest after identity/license correction
      • After fixing the identity match or service plan assignment, have the user sign out and sign in again.
      • If Microsoft 365 identity enforcement was recently enabled, signing off current users can help ensure they reauthenticate with Microsoft 365 credentials.

    Because the same user also fails in the Viva Engage Conversations SharePoint web part, the SharePoint failure is consistent with the underlying Viva Engage access problem rather than a SharePoint-only issue.

    The supported remediation path is therefore:

    • audit the user’s Viva Engage-to-Microsoft 365 identity match,
    • correct any missing or stale Microsoft 365 / Entra ID mapping,
    • verify the user truly has Viva Engage Core or Yammer Enterprise assigned,
    • then force a fresh sign-in.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.