Hi All,
Just a few Hours ago, Microsoft has released the ExchangeOnlineManagement 3.1.0-Previe1 PowerShell Module.
ExchangeOnlineManagement 3.1.0-Preview1 Whats new in this release v3.1.0-Preview1 :
Support for providing an Access Token with Connect-ExchangeOnline. Bug fixes in Connect-ExchangeOnline and Get-ConnectionInformation. Check what Version is installed and what’s available from the PowerShell Gallery
Get-InstalledModule ExchangeOnlineManagement Find-Module ExchangeOnlineManagement -AllowPrerelease Uninstall the old Module and install the Preview Module
Uninstall-Module ExchangeOnlineManagement -Force Install-Module ExchangeOnlineManagement -AllowPrerelease Get-InstalledModule ExchangeOnlineManagement Testing.
Hi All,
Back in April 2022 Microsoft has anounced in theyr Exchange Team Blog, that they will change the Name Attribute of the Objects to the ExternalDirectoryObjectId (EDOID). After some Feedback from Customers and the Community they stopped the Rollout for Reflection as you can read on the Blog post of Tony Redmond.
Exchange Online Plans Changes to Make Mailbox Identification More Effective
Change in naming convention of user’s Name parameter
Hi All,
I have already blogged about the Exchange 2019 Recipient Managemen PowerShell that can Manage Echange Objects without an Exchange Server running.
Install and use Exchange 2019 CU12 Recipient Management PowerShell For Identity and Access Management Systems (IAM) provisioning, management and deprovisioning based in the past on crating a Remote PowerShell to Exchange Server. How do you Address this with the new Recipient Management?
In Fact there are two Solutions:
Hi All,
Today Microsoft has released the ExchangeOnlineManagement-Preview1 PowerShell Module.
ExchangeOnlineManagement 3.0.1-Preview1 Whats new in this release - v3.0.1-Preview1:
Bug fixes in Connect-ExchangeOnline.
Bug fix in Connect-IPPSSession for connecting to Security and Compliance PowerShell using Certificate Thumbprint.
Mitigation for the known vulnerability in Newtonsoft.Json library. More details here: https://github.com/advisories/GHSA-5crp-9r3c-p9vr
Check what Version is installed and what’s available from the PowerShell Gallery
Get-InstalledModule ExchangeOnlineManagement Find-Module ExchangeOnlineManagement -AllowPrerelease Uninstall the old Module and install the Preview Module
Hi All,
With the ExchangeOnlineManagement PowerShell Module 3.0.0, Microsoft has providet the Ability to use Managed Identity in Azure. Time to test that on my own.
ExchangeOnlineManagement 3.0.0 v3.0.0 :
General Availability of REST-backed cmdlets for Exchange Online which do not require WinRM Basic Authentication to be enabled.
General Availability of Certificate Based Authentication for Security and Compliance PowerShell cmdlets.
Support for System-Assigned and User-Assigned ManagedIdentities to connect to ExchangeOnline from Azure VMs, Azure Virtual Machine Scale Sets and Azure Functions.
Hi All,
Over a Year ago i released my first PowerShell Module in the PowerShell Gallery Icewolf.EXO.SpamAnalyze. Now it was time for an Update.
Icewolf.EXO.SpamAnalyze 2.0.8 Whats new in this release:
V2.0.8
Requires now ExchangeOnlineManagement 3.0.0
Addet TenantAllowBlockList checks
Check installed Version and what’s available in the PowerShell Gallery
Get-InstalledModule Icewolf.EXO.Spamanalyze Find-Module Icewolf.EXO.Spamanalyze Uninstall the old Module and install the current one
Uninstall-Module Icewolf.EXO.Spamanalyze Install-Module Icewolf.EXO.Spamanalyze Get-InstalledModule Icewolf.EXO.Spamanalyze There is only one Command you can use
Hi All,
Yesterday on the Patch Thuesday, Microsoft has released Security Updates for Exchange 2013/2016/2019.
The November 2022 SUs contain fixes for the zero-day vulnerabilities reported publicly on September 29, 2022 (CVE-2022-41040 and CVE-2022-41082).
Released: November 2022 Exchange Server Security Updates
Security Update For Exchange Server 2016 CU23 (KB5019758)
After the Reboot i’ve checked the Mitigations. The Mitigation is still active.
.\"C:\Program Files\Microsoft\Exchange Server\V15\scripts\Get-Mitigations.ps1" It’s best practices to run the HealthChecker Script after the Installation of a CU or Security Update
Hi All, It has been almost a Year since i first wrote a Blog Post about the Exchange Online Quarantine Policy. I've already mentioned there, that the Custom Logo does not show up.
Exchange Online Quarantine Policy
https://blog.icewolf.ch/archive/2021/11/05/exchange-online-quarantine-policy.aspx
I had several Microsoft Tickets open regarding that Issue as you can see in my Service request history
I did see that there was an Open Issue since August in the M365 Admin Center Service Health .
Hi All, Recently, Microsoft has anounced the retirement of the legacy mail flow rules (also know als Exchange Transport Rules - Short ETR) in classic Admin Center.
You can add new Exchange Transport rules in the Exchange Admin Center with the new User Interface (UI)
https://admin.exchange.microsoft.com/#/transportrules
These are the Options Regards Andres Bohren
Hi All, A few days ago, Microsoft has anounced the "Quarantine Admin" Role. In the Future you need to be Member of the "Quarantine Admin" Rolegroup to manage the Quarantine.
Manage quarantined messages and files as an admin in EOP
https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/manage-quarantined-messages-and-files?view=o365-worldwide
The "Quarantine Administrator" Role is not yet visible in my Tenant.
If you don't want to wait, you can already create a Custom Role like i did here with the "