A Microsoft file hosting and synchronization service.
Disconnect and reconnect the university account under Windows Access work or school, which resets the device registration used across Outlook, OneDrive, PowerPoint, and the other Microsoft 365 desktop apps for this exact 7ita9/3399811147 sign-in pattern.^1^
Reconnect the Windows account
Disconnecting may temporarily remove access to university-managed resources on this PC. If the device is owned or managed by the university, ask its IT team before proceeding.
- Close every Microsoft 365 application, including Outlook and OneDrive.
- Open Settings → Accounts → Access work or school.
- Select the university account, then select Disconnect.
- Restart Windows after the disconnection. This restart is part of rebuilding the registration, rather than repeating the standalone restart already attempted.
- Return to Settings → Accounts → Access work or school → Connect.
- Sign in with the university account.
- Open one Office application and sign in, then test OneDrive and Outlook.
Because clearing the OneDrive credential and re-registering Windows sign-in components did not help, do not repeat those operations at this stage.
If reconnection does not resolve it
Run the supported Microsoft 365 sign-in diagnostic:
- Open the Windows Get Help app.
- Search for sign in to Microsoft Office.
- Complete the Microsoft 365 sign-in troubleshooter and record its findings.^2^
Microsoft also documents the Support and Recovery Assistant for diagnosing common non-browser Office sign-in failures.^3^
Have the university administrator correlate the failure
The error code alone does not establish whether the failure is caused by licensing, Conditional Access, or the Windows authentication broker. Provide university IT with the displayed:
- Timestamp, including UTC
- Correlation ID
- Affected username
- Application used for the attempt
An administrator with at least the Reports Reader role should:
- Open Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs.
- Filter by Correlation ID and the matching date/time.
- Open the failed event and review:
- Failure reason and sign-in error code
- Authentication Details
- Device Info
- Conditional Access
- Troubleshooting and support
These logs identify the actual tenant-side failure and any policy that interrupted the desktop sign-in.^4^
- If the event shows a Conditional Access failure, IT must address the named policy or device requirement.
- If the event shows an account or authentication failure, IT must correct that tenant-side condition.
- If no corresponding failed event appears, give IT the Get Help results and request investigation of the Windows client registration/authentication path.
Check licensing separately
A license problem should be verified rather than inferred from 7ita9. To inspect the local Microsoft 365 activation state, open Windows PowerShell and run:
cd "$env:ProgramFiles\Microsoft Office\Office16"
.\vnextdiag.ps1 -action list
For 32-bit Office on 64-bit Windows, use:
cd "${env:ProgramFiles(x86)}\Microsoft Office\Office16"
.\vnextdiag.ps1 -action list
The output shows the installed product, activation user, tenant, license type, and whether its state is Licensed.^5^
If it is not licensed, university IT must verify that the account has a Microsoft 365 plan containing desktop applications. Do not reset activation unless the diagnostic or administrator confirms an activation-state problem.
References
- Correlation Id: [Moderator note: personal information removed] Timestamp: 2025-11-26T13:17:04.000Z DPTI: [Moderator note: personal information removed] Message: An unexpected error occurred. Tag: 7ita9 Code: 3399811147 - Microsoft Q&A
- Access work or school troubleshooter for restoring access to M365 desktop applications | Microsoft Support
- How to troubleshoot non-browser apps that can't sign in to Microsoft 365, Azure, or Intune | Microsoft Support
- Troubleshoot sign-in problems with Conditional Access
- Check the license and activation status for Microsoft 365 Apps