Pinned Posts
Forum Widgets
Latest Discussions
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.
Problems sharing files with users outside Tenant
An additional Sign In window appears for external users with whom we share files or folders through OneDrive and/or SharePoint. The window for entering the email appears (to validate that it's the intended recipient), but before entering the verification code, the Organization Sign In window appears. This sometimes requests a password, which can cause issues or even prevent users from sharing these folders with external users. Authentication flow example: Normally, step 2 is followed by step 4, but in my case, it's taking me to step 3 where I have to re-enter the email address I'd already entered in step 2. This isn't normal. In this case, there's no major problem with this email because it then asks for the verification code, and I log in without a problem. But for example, when I tried another email address, also from Gmail, it asks for a password to authenticate: Then I realized it's asking for my password because that email is associated with my GitHub account, and it's trying to authenticate with a password. However, this flow is incorrect because for authentication to SharePoint files shared with external users of the Tenant, it should only ask for the username and verification code. The fact that it asks me to enter my email twice, as in step 3 of each example, and that it occasionally asks me for a password, is incorrect in the flow, and I don't know how to change that.
Error installing Apps 365, command not supported.
I was performing an Online Repair for a user. It did the uninstall fine, but then threw this error. I tried to reinstall, same error. Used the MS Cleanup tool, ran SFC, cleared temp files, cache... Internet connection is stable. Disabled security software (Zscaler). I'm out of ideas. I'm hoping someone has seen this before. Thanks for any help!
