Hi All, Do you know the User reported Settings in Microsoft 365 Defender for Office 365? For instance, you can send the Mails that a user reports with the "Report Message" Add-In to Microsoft also to a reporting Mailbox that you own.
User reported settings
https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/submissions-user-reported-messages-custom-mailbox?view=o365-worldwide User Reported Settings
https://security.microsoft.com/securitysettings/userSubmission I've enabled that a while ago. As you can see the Reporting Mailbox receives all types: - Junk - Phishing - Not Junk
Hi All, A few hours ago a new Version of the Microsoft Defender for Office 365 Recommended Configuration Analyzer (ORCA) Module has been released. ORCA 2.2
https://www.powershellgallery.com/packages/Orca/2.2
To check the installed Module and what's available on PowerShell Gallery use the commands below
Get-InstalledModule ORCA Find-Module ORCA Uninstall the old and install the new PowerShell Module
Uninstall-Module ORCA Install-Module ORCA Get-InstalledModule ORCA The Module only contains two Commands Get-Command -Module ORCA
Hi All, Yesterday, Microsoft has released the ExchangeOnlineManagement 3.2.0-Preview1 PowerShell Module to the PowerShell Gallery.
ExchangeOnlineManagement 3.2.0-Preview1
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0-Preview1
Whats new in this release: v3.2.0-Preview1 : 1. Preview Release of new cmdlets: - Updating Briefing Email Settings of a tenant (Get-DefaultTenantBriefingConfig and Set-DefaultTenantBriefingConfig) - Updating Viva Insights Feature Settings of a tenant (Get-DefaultTenantMyAnalyticsFeatureConfig and Set-DefaultTenantMyAnalyticsFeatureConfig) 2. Bug fixes in Connect-ExchangeOnline. Let's check what Version of the Module is installed and what is available from the PowerShell Gallery
Hi All, Sometimes you need to check the Exchange Active Directory Versions to see if a Schema Upgrade is needet. It is well documented on the Website from Microsoft
Exchange Active Directory versions
https://learn.microsoft.com/en-us/exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-2019#exchange-active-directory-versions
In this Case we use ADSIEdit.msc
Or you simply run this Script
###############################################################################
# Get Exchange AD Schema Version
###############################################################################
#Needs ActiveDirectory PowerShell Module
# Exchange Schema Version
$sc = (Get-ADRootDSE).SchemaNamingContext
$ob = "CN=ms-Exch-Schema-Version-Pt," + $sc
Hi All, In this Article i'll show you how you can "Search and Purge" Emails in Exchange Online. With Compliance Search you can search for Mails and purge (Soft- or HardDelete) them afterwards. That's usually the case for Phishing or Spam Incidents.
Your search can cover a maximum of 50’000 Mailboxes
A new Compliance Search will create an Alert by default.
First of all you need to have the correct Permissions https://security.
Hi All, Last Night the February 2023 Exchange Server Security Updates have been released.
Released: February 2023 Exchange Server Security Updates
https://techcommunity.microsoft.com/t5/exchange-team-blog/released-february-2023-exchange-server-security-updates/ba-p/3741058 Description of the security update for Microsoft Exchange Server 2019, 2016, and 2013: February 14, 2023 (KB5023038)
https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-february-14-2023-kb5023038-2e60d338-dda3-46ed-aed1-4a8bbee87d23
Security Update For Exchange Server 2016 CU23 SU6 (KB5023038)
https://www.microsoft.com/en-us/download/details.aspx?id=104999
The downloaded exe File extracts then starts the Installation in a elevated Promt
After the Security Update is installed, it is a good idea to restart the Server.
Hi All, If you still use "Exchange Online PowerShell with MFA" aka "ExchangeOnline_V1" PowerShell Module - it is time to Upgrade. Instead of using the ExchangeOnlineManagement V2 i recommend to use the V3 Module wich is GA since a few Months.
ExchangeOnlineManagement 3.1.0
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.1.0
The old PowerShell Module still can be downloaded in the "Classic Exchange Admin Center"
That's the Link on the Desktop
Here's the Info Message you receive when using this PowerShell
Hi All, In the Microsoft 365 Message Center https://admin.microsoft.com/#/MessageCenter there is an Announcement about Test-Message where you can test the Transport Rules and DLPRules.
FIX: Exchange Transport rule (ETR) or Data Loss Prevention (DLP) rule is not working as expected
https://techcommunity.microsoft.com/t5/security-compliance-and-identity/fix-exchange-transport-rule-etr-or-data-loss-prevention-dlp-rule/ba-p/3033869 Test-Message
https://learn.microsoft.com/en-us/powershell/module/exchange/test-message?view=exchange-ps Test-Message -Sender m.muster@icewolf.ch -Recipients postmaster@icewolf.ch -SendReportTo a.bohren@icewolf.ch -TransportRules -UnifiedDLPRules
Let's have a look at my Transport Rules Get-TransportRule
Now i get two Reports: "Transport Rule Tracing Report"
Hi All, I've already blogged about Exchange Online PowerShell V2 and Modern Auth with Application in AzureAD (Step-by-step) Azure AD Application Registration Permission: Office 365 Exchange Online > Exchange.ManageAsApp Add AAD App to Azure AD Role "Exchange Administrator" or "Exchange Recipient Administrator"
In this Article it's about custom RBAC Roles and Application Authentication Azure AD Application Registration Permission: Office 365 Exchange Online > Exchange.ManageAsApp Create a Exchange Online Service Principal for the Azure AD App
Hi All, New opt-in endpoint for POP3/IMAP4 clients that need legacy TLS
https://techcommunity.microsoft.com/t5/exchange-team-blog/new-opt-in-endpoint-for-pop3-imap4-clients-that-need-legacy-tls/ba-p/3710395
Exchange Online ended support for TLS1.0 and TLS1.1 in October 2020. This year, we plan to disable these older TLS versions for POP3/IMAP4 clients to secure our customers and meet compliance requirements. However, we know that there is still significant usage of POP3/IMAP4 clients that don’t support TLS 1.2, so we’ve created an opt-in endpoint for these clients so they can use TLS1.