Tell us more null subjects and MessageID scenario. You are currently able to query the time.
The functionality to make it possible to change the name of an O365 tenant, especially with Sharepoint Online in mind, is being planned. There is no ETA at this time though.
1,116 votestry this instead · AdminMicrosoft 365 Groups Feedback (Product Owner, Microsoft Office 365) responded
Disabling the welcome mail is possible with an extra parameter in the Set-UnifiedGroup cmdlet in Exchange PowerShell: -UnifiedGroupWelcomeMessageEnabled:$false. See https://docs.microsoft.com/en-us/powershell/module/exchange/users-and-groups/set-unifiedgroup
Use this as a part of a custom group creation flow if you would like to restrict and/or customize the welcome mail for many groups across your tenant.
Thank you to everyone taking the time to vote on this ask. Our security best practices recommend not making passwords expire and our focus is around this policy at the moment. You can read more about it in these two documents:
We plan on implementing this functionality, although we do not have any timelines to share at this stage.
Today, based on feedback, we’ve lowered the timeout to 24 hours. In the future, we are planning more improvements, although we do not have any dates or details to share at this time. Thank you for the continued feedback.
An error occurred while saving the commentAnonymous commented
Please prioritize and fix this issue. It is really a big problem when trying to ensure encrypted transmissions. We cannot wait 2 days for TLS enforced connections to fail, when sending to non-TLS supported recipients - it should be instant. The server will not begin supporting TLS just because it tries for 2 days. We use Office Message Encryption when it fails for non-TLS supported recipients, but having to wait several days to be adviced an e-mail cannot be delivered is unacceptable for our usage. Thank you!
Azure Active Directory Conditional Access has functionality for “Countries/Regions” – see https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition
That said, the most effective protection you can have against password spray attacks is to enable MFA and disable basic authentication. If you cannot do this for your entire organization, then blocking user access to legacy protocols like POP, EWS, IMAP and SMTP is another step you can take. Exchange Online Client Access Rules can help you to further customize (https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/client-access-rules/client-access-rules). For additional recommendations, please see Office 365 Secure Score.
That said, please know that we are listening to feedback and working on solutions to help make Office 365 users more secure. Thank you for the feedback.