Shortcuts appearing when using Option+arrow in Outlook on Chrome in Mac
luse Outlook on Chrome in my MacBook Pro. While typing an email, though, if I use Option tarrow left or right (to go back or forth between words), after a few words, the shortcut letters for the menus pop up, and stop what I'm doing. (See image.) It doesn't happen in any other window on Chrome. So it's not a Chrome thing. It's only when Outlook 365 is loaded. (Don't know if it happens in other 365 apps, as I only use Outlook, really.) Anyone experienced that? And, if so, is there a solution? I tried Outlook 365's setting, but nothing there. Thanks!
Generating an email with Power Automate using data from MS Forms
I'm trying to generate an email based on responses to a Microsoft Form. To do that, we've been using Power Automate. But I don't know coding, so I'm struggling with the "if this, then do this or if this then do this." I'm trying to add content based on the response to a form question. This is what I have & Power Automate doesn't like it. If possible, I want the No response to result in a blank. if(equals(outputs('Get_response_details')?['body/r4dc7982d2d21447595928fe605d196a9'],'Yes','SNAP',' ') It also doesn't like this: if(equals(@{outputs('Get_response_details')?['body/rfa090ef4e8d14bf187d32d6ee29bce37']},Yes),'What is needed to complete the benefit request? @{outputs('Get_response_details')?['body/r6671aa148c974fbfb399bdf3c334f4a4']}',' ')
IS EXCHANGE 2016 HYBRID STILL SUPPORTED?
IS EXCHANGE 2016 HYBRID STILL SUPPORTED as of January 2026? Pls advise if this statement is correct: Exchange Server 2016 was supported for hybrid deployments with Exchange Online, but as of October 14, 2025, it is no longer supported by Microsoft, meaning no security updates, bug fixes, or technical support are provided. While hybrid prerequisites still technically list Exchange 2016, running it now carries security and compliance risks, and Microsoft recommends upgrading to a supported version such as Exchange Server Subscription Edition or moving fully to Exchange Online. Continuing to use Exchange 2016 in hybrid is possible, but unsupported, so for a secure and compliant hybrid setup, an upgrade or migration is strongly advised.
Outlook Classic for M365 - File > Encrypt > 'Encrypt-Only' option applies 'Do Not Forward' label?
I recently joined a new company and am helping support their M365 tenant and admin duties. I'm running into a very weird issue where no recipients can actually read/view the message when we encrypt emails using only 1 specific method (our organization largely uses the Outlook Classic for Microsoft 365 desktop app). If a user follows this method, for some reason the 'Do Not Forward' label is applied to the encryption, despite specifically selecting 'Encrypt-Only' - it defaults to 'Do Not Forward' every single time: New Email > File > Encrypt > Encrypt-Only Sending emails with this method gives any/all recipients a "You don't have sufficient permissions to open the mail." regardless of where they try to open the email (OWA, Outlook Classic, New Outlook) Yet, if the user tries this other method below - the proper Encrypt-Only label is applied, and any Outlook client immediately and opens/views the email as you'd expect: New Email > Options ribbon > Encrypt properly applies the Encrypt-Only label I verified IRM (Identity Rights Management) is enabled for our tenant: And encryption tests pass with flying colors: Ultimately, I'm at a loss for what's going on here and specifically where to check to fix this issue for this 1 specific encryption method. Poking around in the Purview portal, I'm having a hard time figuring out where these encryption policies/settings lie and how to get this method to stop defaulting to 'Do Not Forward' even though 'Encrypt-Only' is checked.Does MC1189663 Impact Standard Power Automate Approvals?
Hi everyone After reviewing the change described in MC1189663 (retirement of external access tokens for actionable messages), I'm unsure wheter this also affect the out-of-the-box Standard Approval action in Power Automate. My question is specifically about the default "Start and wait for an approval" / "Standard Approval" action with no special configuration. Does this change impact approval emails or actionable messages generated by the Standard Approval action for internal usage (mails to internal accounts), or will those continue to work without modification? Thanks in advance for any clarification.Rules for Outlook (new) makes no sense.
I have tried now to use the new version of Outlook for both private and work use. Whenever I set up rules in classic Outlook, I always had to add a sound notification or for it to show me a desktop alert. Because if I have a rule that says "If I receive e-mail from person X, move to folder Y" I do not get a notification, and I risk missing them (which has happened a lot previously). Imagine my shock when I see that the new version of Outlook has dumbed down the rules significantly and restricted me to how I can use them. Is there a reason why we cannot add "show desktop alert" or for it to play a sound in the "actions" tab? I do not understand why this feature was removed, as well as removing auto archiving. I just don't understand why! Will the option for adding desktop alerts and for it to play sounds be added in the future?Outlook is sending duplicated mails
Hello dear Microsoft Community I've got following problem: With one of our clients there is an issue with Outlook/Mailing The mailbox is IMAP If he sends Mails to someone they'll recieve the sent message, for like 20 times. the only suspicous thing is, that we can see 3 duplicates of that mail in the 'sent' folder. but regardless it was recieved alot more than 3 times, either way. Do you have an idea ? I already updatet Microsoft Windows & Microsoft Office 365 made a new profile checked for Add-Ins or antivirus applications I also looked it up on our firewall we also checked the log on the mailserver greetings and im looking forward to recieve some help from YOU
Title: Expose SHA-256 or SHA-1 for Mail Attachments in Microsoft Graph
Problem Email attachments in Graph don’t include a content hash. To identify or match attachments, developers have to download the entire file first. That wastes bandwidth and time and increases exposure. OneDrive/SharePoint already return hashes, but mail does not, so experiences are inconsistent. Request Add a server-provided content hash to every mail attachment. Prefer SHA-256. If that’s not feasible initially, expose SHA-1 as a minimum to align with existing Drive item hashes. Benefits Faster and cheaper: avoid downloading large files just to tell if you already have them. Deduplication: detect repeated attachments across threads and mailboxes. Security operations: correlate attachments with threat intel by hash and triage suspicious emails without fetching payloads. eDiscovery and compliance: confidently match the same document across mail and files. Consistency: a predictable, uniform approach across Mail and OneDrive/SharePoint.
GoDaddy to Microsoft 365 Email Account Transfer
Hi all, I'm working with a small company that just updated its business name. They want to update their Microsoft 365 licences to the new domain, which is currently registered with GoDaddy. As they weren't ready to change this straight away, some 365 (essential) Email accounts were set up in GoDaddy. Now they are ready to make the 365 update, but the email situation seems really confusing, and the two options seem to be: 1) delete the accounts and set them up again, 2) use GoDaddy to manage the changeover - but the tech support seemed a little vague on this and the timings. Has anyone used the GoDaddy managed change and was it successful? Or would you recommend doing it manually? (Or another option?) Sorry, I know versions of this have been asked before, but I'd really appreciate some up-to-date advice if possible. Thanks very much!
