Outlook 2016 blank MFA screen for some users
I have a Conditional Access rule so that when someone connects from outside a trusted IP it requires MFA, I have a few users that get the "Requires password" message come up, they get a window and type in their username and click next, then the window disappears without prompting for MFA and it's back to where they were. Same thing if they go to File->Accounts if they are signed out and try to sign in they get asked for Email and then it just closes and they are still signed out. It's not for all users and everyone is using the same Office 365/2016 installation, monthly channel 1903, we use ADFS
Office 365 no internet error
Outlook just stopped working yesterday. I have been using 356 for a couple of years now. One drive and Outlook both say I don't have internet access. Obviously I do. I can use one drive and outlook via a web browser, but not the desktop apps. I have tried most of the suggested fixes and nothing has worked. Anyone else having issues?
ARC verification fail (40) on specific Exchange Online frontends - recurring issue
Hello, We are observing recurring arc=fail (40) errors on messages forwarded through Exchange Online, caused by specific frontend servers. The same messages pass ARC verification correctly on other providers (Google, etc.). Affected frontends identified so far: CH2PEPF0000013F.namprd02.prod.outlook.com - build 15.20.9700.17 (March 14, 2026) CH3PEPF0000000B.namprd04.prod.outlook.com - build 15.20.9769.17 (April 6, 2026) Both share the same build suffix .17. The signing implementation on our side has been cryptographically verified as correct and RFC 6376 compliant. The issue has also been reported on the IETF ietf-smtp mailing list with full technical analysis. Cryptographic analysis shows the failing servers append a spurious trailing \r\n to the last header before computing the verification hash, violating RFC 6376 Section 3.7. Is there a pattern with .17 frontend builds and ARC verification? Reagards VittorioOffice 365 issues
We have an end user that started with us approximately a year ago. Shortly after he started he began noticing that his status would go away on a fairly regular basis on MS Teams. We tried uninstall/reinstall, resetting, repairing and the problem persisted. Since he was a relatively new hire we were thinking it was something with his laptop so we replaced and the issue returned. Turned in a ticket with our Office 365 vendor who in turn opened a ticket with Microsoft. After some initial testing they sent a Teams install file that seemed to fix the issue. Since that time he has regularly had issues with Teams disconnecting, Outlook just stop receiving emails, while showing connected. Typically the only fix was a restart and on some occasions that did not work. Sometimes a reset or repair might fix this issue. Throughout this we did clear credential manager, caches, etc...This got a point yesterday where I created a new user profile for him, basically like a new laptop and it temporarily fixed the Teams and Outlook issue, however when attempting to sign into MS Edge it would just spin and had to use task manager to close the app. Tried a repair on the app as you cannot uninstall and same result it would hang up and have to forcibly closed. Just wondering if someone else has encountered something like this and possible fixes. ThanksOAB download fails after hybrid mailbox move.
Hi folks, I'm posting this query here as I doubt anyone in the Outlook forums would have the necessary Exchange hybrid knowledge. I run a classic hybrid Exchange environment where Exchange Server 2019 CU15 is the on-premise platform. Authentication is provided by on-premise AD FS, with the accounts being synchronised from on-premise via AAD Connect. I've just moved my on-premise mailbox to Exchange Online via New-MoveRequest and for the most part, everything is fine. One thing that possibly isn't fine - going off the Bits-Client event log is the regular offline address book downloads, where I'm seeing regular failures in the event log and through double-checking with bitsadmin.exe. The initial address book synchronisation worked as the view in Outlook is fully populated, however, I expect that future changes likely won't come through. bitsadmin output Event log output (There's numerous events to choose from - this is the one I'm most curious about.) The BITS service provided job credentials in response to the UNIDENTIFIED authentication challenge from the outlook.office365.com server for the Microsoft Outlook Offline Address Book <guid> transfer job that is associated with the following URL: /OAB/<guid>/oab.xml. The credentials for the <sid> user were rejected. When the mailbox was on-premise, the OAB came from the Exchange Server - no surprise there, where post migration it can be seen from the bitsadmin output it now comes from outlook.office365.com. Perhaps that's also to be expected - I don't know, but it makes sense given the move. What alerted me to there potentially being an issue is the systray icon frequently gets stuck on the "synchronising" icon, and running a manual full OAB sync from within Outlook fails to complete. After an extended "hang" period, the sync window eventually times out with the error shown above (the protracted UI behaviour would appear to be due to the large number of retries). Dropping the BITS job URL into Edge simply returns a HTTP 503, which doesn't necessarily strike me as a problem. After all, I'm unable to provide a BEARER token using this method. I haven't yet tried via PowerShell as it only occurred to me now but perhaps I'll do so after posting this. Searching on this error and scenario has turned up nothing useful. I have also checked and compared event log entries from an Azure AD-native account, where it's a mixed bag of successful OAB BITS downloads and unsuccessful ones that feature the same symptoms as above, which offers up the possibility this might be a transient service-side error (though I'm not leaning heavily towards this). Has anyone else encountered this issue and resolved it? Is it even an issue to begin with, or is this expected behaviour? I'm unsure what to make of the symptoms. Cheers, LainTwo Linked Outlook Issues Causing Accidental Emails to Wrong Clients Feature Request + Bug Report
Hi Outlook Community, I'm posting this after a real incident at work where I accidentally sent a confidential email to the wrong client. After reflecting on what went wrong, I've identified two separate but related Outlook issues that compounded the mistake and I want to raise both here so they reach the right people. Bug: Autocomplete Recipient Changes After You Press Enter This one is subtle but dangerous. When you start typing a name in the To/CC/BCC field, Outlook shows an initial autocomplete suggestion. If you press Enter before the search fully resolves, the dropdown refreshes mid-selection and the contact that actually gets added is *different* from the one that was highlighted when you hit Enter. You don't get any warning. You believe you've selected the right person. You haven't. I've submitted this via the Feedback Portal here: https://feedbackportal.microsoft.com/feedback/idea/9a32197e-5424-f111-9730-0022485314bc Suggested fix: Freeze the highlighted contact reference at the moment Enter/Tab is pressed, independent of any ongoing background search refresh. --- Feature Request: Cross-Domain Recipient Warning (like the missing-attachment check) Outlook already warns you before sending if it detects you may have forgotten an attachment. I'd love to see a similar pre-send check for this scenario: You are about to send an email to recipients across 3 different organisations. Did you mean to do this? In consulting, legal, finance, and any client-facing role, it's very easy to accidentally include someone from Client B on an email meant only for Client A especially when contacts share similar names. A configurable domain-count threshold (default: 2 external domains) with a soft confirmation prompt would catch this class of mistake before it becomes a compliance incident. Key asks: - Configurable threshold (user-level) - Domain whitelist support (e.g., always allow your own org + a known partner) - Covers To, CC, and BCC combined - Non-blocking same UX pattern as the attachment warning I've submitted this as a feature request here: https://feedbackportal.microsoft.com/feedback/idea/9a32197e-5424-f111-9730-0022485314bc --- Has anyone else run into either of these? Would love to know if the autocomplete bug is reproducible for others that would help push it up the priority queue. Thanks for reading. Sudharm P
Can we hide default address lists in Outlook Address Book and show only custom ones?
There are existing Custom Address Lists. When users use the MS Outlook App (Office 2019) and open the Address Book, is it possible to hide the other address lists (including domain-sg-GAL, Global Address List, and domain-sg-Rooms), and only display the Custom Address Lists (domain-HK-AL and domain-sg-AL) — the ones shown in green in the photo?
Issue with viewing mode for E5 licensed users
I'm a sysadmin for a Health care provider in Sweden and we have an issue with users with an E5 license loading into Office apps in view-mode. As far as I know we are a coupe of organisations providing health care that have this same issue. Background: We have a mix of F3 and E5 licenses and sometimes the F3 licensed users need to view documents that contains info that isn't allowed to be saved in the cloud. To minimize the popups that show up when a user starts word unlicensed we have a GPO (viewer mode) that says that it should open i view-mode. Per my understanding this GPO is device based and not user based. However, this also affects the users of E5 license who regularly change workstations, easily 5-10 devices in a day. Since they should be able to view and edit documents in office apps it causes frustration and confusion when they load into view-mode and have to log out and then in again (or update license) and restart the program. Our computers devices are Microsoft Entra hybrid joined and shared computer licensing is enabled. Are there any solutions or viable workarounds for this issue? It's not complicated for users to handle but frustrating and causes a lot of tickets to the support team. Unsure if I'll be able to participate due to the time zone difference but will appreciate any and all help. /Per Ekholm
