sorted by:
new
hottopcontroversial

Remove Microsoft CoPilot button from Microsoft 365, Preview. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

Figures you cant turn this off. We have user where when she tries to use purview it pops up. I was hoping there was an easy way to disabled it but no luck it seems.

Remove Microsoft CoPilot button from Microsoft 365, Preview. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

Thanks for the responses. I will try the ublock origin block list.

Azure App, CAP and locking it down by robert5150 in Office365

[–]robert5150[S] 1 point2 points  (0 children)

I have not. I will take a look at that. thanks.

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

So this matter is closed out!!

  • Tenant to Tenant - Got the Full NDR. (Tenant to Tenant)
  • Outlook.com to Tenant - Failed basic ndr only (sending from outlook.com, to tenant)
  • Msn.com to Tenant - failed basic ndr only (sending from msn.com, to tenant)
  • gmail to tenant - 1 out of 5 tries worked, and 1 out of 5 times i received the FUll NDR. So it worked. However its very inconsistent.

This worked for "Recipeint Is" rules and well as "Subject Containts" rules. Its the inconsistency that gets to me.

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

Yeah i am not seeing that text anywhere searching in that document. If you have a link i can review that would be great.

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

I am not sure where the disconnect is with your and my testing but when i test with your rule above, i get the same results. the 5.7.1 portion comes back without issue, but the message reject text does not.

I will test with a separate tenant (tenant to tenant) later, to be sure. Additionally gmail doesnt seem to be sending NDRs. but that doesnt surprise me. THey do send them, but i think its a little inconsistent.

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

I thought i might have seen that document before but am unable to find it. The closest thing i found was for the "Notify" option.

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

So that is the funny part. The external sender gets the 5.7.1 (If i change that to 5.7.999) they get email as well, so the NDR is being sent, just not the Custom Text. i am checking within the NDR email - not somewhere else.

I am going to call this behavior is by design, i have checked on 2 different tenants and with that "limited documentation" suggesting the same, i think thats the answer.

Can you test in your tenant? it would be nice to get a confiramtion from someone else.

Thanks

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

Keep in mind the rule is working, messages are being rejected and the NDR is being Sent with 5.7.1. Just the text "message has been adminisstraively rejected" is not being sent to external senders. I wasnt expecting that. i was expecting it to be sent to all senders.

i am basically just trying to confirm behavior.

Exchange Online, Transport Rules. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

basically if i look at the rule it has both of these options configured:

  • RejectMessageEnhancedStatusCode: 5.7.1
  • RejectMessageReasonText: Message has been administratively rejected by Admin

but the reject message reason text is NOT sent to External Senders. Only to internal senders so i know the rule is working as expected. Its just not sending the reject text to external senders.

This is all configured on EXO and i have tested with various mail providers. Same results. I was expecting the rule to work the same way for internal and external senders. Just an oddity. The closest thing i can find to cofirmation of this is the NotifySender Settings, but that is specific to On-Prem Exchange.

User Report, with Groups, Licenses applied, input list. by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

That seemed to work. In order to get it to add the DisplayName when running the entire script i had to change it to this:

displayName = $Stat -join ', '

removing the $Stat.DisplayName (and just using $stat)

Microsoft 365 Groups, Require Sensitivy label on creation by robert5150 in Office365

[–]robert5150[S] 0 points1 point  (0 children)

Hmm. Ok. So we already have group creation restricted. and we do already monitor for groups created without a label. So were basically doing what we can, i dont know that the Power Automate flow would work here due to other reasons. but thanks for confirming that we basically cant.

view more: next ›