Скачать или смотреть Fix!!!! Working Offline Problem in Outlook 2019

This issue was posted to the Service Health Dashboard (SHD) as incident EX186942 starting at July 31 2019 11:00 AM (UTC). The user experience of this incident is: Users with multiple enterprise sign-in accounts can't connect to Exchange Online via the Outlook desktop client. A suggested workaround is:

1) Close Outlook and other Office applications.

2) Open an Office desktop application, such as Word, PowerPoint or Excel.

3) Navigate to File --- Account -- Switch accounts, and then click the ellipsis next to the account that's not having the problem.

4) Click Sign out and then OK.

*Note: Users that have multiple accounts may find it difficult to determine which account to sign out of; though, they should be able to sign back in later if there is an issue with this process.

5) Close the Office application used for this process and re-start the Outlook desktop client.

6) When prompted for a password, click "sign in to a different account" and enter the correct information.

Symptoms
After you enable modern authentication in an Office 365 tenant, Microsoft Outlook cannot connect to a mailbox if the user’s primary Windows account is a Microsoft 365 account that does not match the account they use to log in to the mailbox. The mailbox shows “Disconnected” in the status bar.

Cause
A known issue in Office creates a miscommunication between Office and Windows that causes Windows to provide the default credential instead of the appropriate account credential that is required to access the mailbox.

This issue most commonly occurs if more than one mailbox is added to the Outlook profile, and at least one of these mailboxes uses a login account that is not the same as the user’s Windows login.

Resolution
The most effective solution to this issue is to re-create your Outlook profile.

For Monthly Channel Office 365 subscribers, the fix to prevent this issue from occurring is available in builds 16.0.11901.20216 and later.

For Semi-Annual Customers, the fix is included in builds 16.0.11328.20392 and later.

For devices that are already affected by this issue, refer to the Resolution section.