Category: Microsoft

The original GetExchangeURLs.ps1 script was written by Paul Cunningham to provide a simple way to display Exchange Server Client Access URLs from a single PowerShell script. Ali Tajran later updated the script to version 1.10, adding the PowerShell virtual directory and reorganizing the output. I recently revisited the script and decided to continue the same approach rather than create a completely new one. The result is Get-ExchangeURLs-v2.ps1. View / Download the PowerShell Script View Get-ExchangeURLs-v2.ps1 The script opens directly in the browser so the contents can be reviewed before saving or running it. Version 2 keeps the original read-only URL reporting concept, but updates and extends it with additional options for authentication visibility, service filtering, multi-server output, grouping, and text-file export. What Changed in Version 2 The main changes added…

While validating a fresh Exchange Server 2019 CU15 installation, I started capturing the default configuration before making any namespace, certificate, or authentication changes. One of the first checks was Get-ExchangeCertificate. Unexpectedly, the cmdlet returned only the column headers and no certificate objects, even though the Exchange Admin Center showed the certificates normally. PowerShellGet-ExchangeCertificateGet-ExchangeCertificate Thumbprint Services Subject ---------- -------- ------- At first, this looked like the known Exchange Auth Certificate issue associated with PowerShell Serialization Payload Signing. However, the Auth Certificate was present, valid, correctly configured, and Microsoft's validation script reported no problem. What initially looked like a certificate problem eventually turned out to be related to the timing of certificate activation and HMAC key selection. Certificates were present and the Auth Certificate was valid The Exchange Admin Center showed all…

In Exchange Hybrid environments, it is common to use mail flow rules to add an external disclaimer or warning banner to messages received from outside the organization. A typical warning may look like this: WARNING: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender. This is a good security control. It helps users identify messages that came from external sources. However, there are some scenarios where messages generated by internal application servers may also receive this external disclaimer. This usually happens when an internal application server submits email anonymously to Exchange Server on-premises, and Exchange then routes the message to Exchange Online. In this article, we will look at how to handle this scenario safely by using a custom header…

Microsoft recently published guidance for Exchange Server addressing the May 2026 vulnerability. One important note in the article is related to OWA Light. Microsoft states that OWA Light — accessed by using an OWA URL ending with /?layout=light — does not work properly after the mitigation is applied. Microsoft also notes that this feature was deprecated several years ago and is not intended for regular production use. This can become a practical issue if some users previously selected the following option in Outlook on the web: "Use the light version of Outlook" When this option is selected, the user may continue to be redirected to the Light version of OWA even when accessing the normal OWA URL. Example URLs: https://mail.contoso.com/owahttps://mail.contoso.com/owa/?layout=light The Issue In the lab I confirmed the following behavior:…

In Exchange Hybrid environments, shared calendar behavior after mailbox migration is often misunderstood. Many assume that calendar access breaks when a mailbox is moved to Exchange Online. In reality, the outcome depends on how permissions were configured before the migration. This article walks through a controlled scenario and shows exactly what happens. Scenario We use two users: buser01@onpremx.com bmuser01@onpremx.com Initial state: Both mailboxes are on on-prem Exchange Users can access each other’s calendars Step 1 – Test Default Behavior (On-Prem → On-Prem) Without assigning any permissions: Add calendar in Outlook Calendar is added successfully Only free/busy information is visible No subject or details This is expected. Default calendar permission: PowerShellAvailabilityOnlyAvailabilityOnly Step 2 – Check Existing Permissions Verify current permissions: PowerShellGet-MailboxFolderPermission bmuser01:\Calendar Get-MailboxFolderPermission buser01:\CalendarGet-MailboxFolderPermission bmuser01:\Calendar Get-MailboxFolderPermission buser01:\Calendar Typical result: No explicit…

You have just moved some mailboxes from one Exchange 2010 SP1 ( or later ) mailbox database to another mailbox database but all the moved mailboxes are shown in disconnected mailboxes. This happens because of the "Soft Deleted mailboxes". Exchange doesn?t fully delete the mailbox from the source database immediately after completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state. The soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires or you use the Remove-StoreMailbox cmdlet to purge the mailbox.   You can see soft-deleted mailbox by running the following shell command Get-MailboxStatistics ?Database ?Mailbox Database Name? | Where-Object {$_.DisconnectReason ?eq ?Softdeleted?} You can delete all soft deleted mailboxes from a particular Mailbox Database by…