Explore technical insights and updates for Office 365 and Exchange Server. Priasoft empowers IT professionals with reliable solutions and expertise.

Priasoft - Email Blocking
Last reviewed: April 2026 — checked against current Microsoft product lifecycle and Exchange Online enforcement timelines.

Microsoft has issued an alert regarding the risks of unaddressed Exchange Server patching and security issues that can impact email delivery speed and potentially lead to email throttling if not addressed. If these issues are not resolved within 30 days, emails may be blocked, causing severe disruptions in communication with customers and partners. Read on for vital information on how to mitigate these risks and safeguard your email operations.

Microsoft’s recent announcement highlights that unresolved issues on unsupported or outdated On-premises Exchange servers can result in security and other potential risks. Customer should address these issues as quickly as possible to avoid Microsoft taking action in the form of email throttling, causing significant delays in email delivery. This can lead to missed opportunities, frustrated customers, and damaged business reputation. However, the urgency goes beyond that. If these issues are not addressed within 30 days, Microsoft may take further action and block emails from these servers, resulting in disruptions in communication.

We’ve said many times that it is critical for customers to protect their Exchange servers by staying current with updates and by taking other actions to further strengthen the security of their environment, Microsoft

To avoid such consequences, it’s crucial to take immediate action. Here are critical steps to protect your business:

  1. Address Known Issues: Conduct a comprehensive review of your Exchange servers for any known issues or errors and resolve them promptly. This may involve applying relevant patches, updates, or configuration changes to eliminate potential bottlenecks in email delivery.
  2. Keep Exchange Servers Up to Date: Ensure your Exchange servers are running the latest supported version and have all the necessary security updates applied. Regularly monitor for new updates and apply them promptly to maintain a secure and reliable email communication environment.
  3. Monitor Email Delivery Speed: Keep a close eye on the speed of email delivery from your Exchange servers to Exchange Online. If you notice significant delays, investigate and resolve any potential throttling issues promptly to prevent prolonged disruptions.
  4. Seek Expert Assistance: If you’re unsure about the status of your Exchange servers or need help with addressing issues and monitoring email delivery speed, consider seeking assistance from IT professionals or Microsoft support for timely resolution.
  5. Leverage the new Mail Flow Report: Microsoft will release and new report in the Admin Center that will provide information about Exchange servers that are unsupported in their environment.

The risks of unaddressed issues on your on-premises Exchange servers are imminent, with the potential for email throttling and complete blockage within 30 days. Don’t wait for disruptions to occur – take immediate and proactive steps to address known issues, keep your Exchange servers up to date, monitor email delivery speed, and seek expert assistance if needed.

In conclusion, Microsoft’s urgent alert underscores the need for immediate action to mitigate risks and ensure uninterrupted email operations. Take the necessary steps to address issues, keep your Exchange servers up to date, monitor email delivery speed, and seek expert assistance if required. By taking proactive action now, you can prevent email throttling, potential blockage, and maintain seamless email communication with your customers and partners. Act urgently to safeguard your business from the risks of unaddressed issues on your Exchange servers.

To learn more see Throttling and Blocking Email from Persistently Vulnerable Exchange Servers to Exchange Online.

Office365 Secret Cloud

Microsoft Office 365 is now available for US National Security Missions.

The Office 365 Secret Cloud provides a secure and compliant cloud environment for classified communications and collaboration. This capability is critical for national security agencies that need to protect sensitive information from cyber threats and foreign adversaries.

The Office 365 Secret Cloud is built on Microsoft’s Government Community Cloud (GCC) High infrastructure, which has been authorized by the Department of Defense (DoD) for Impact Level 5 (IL5) workloads. The IL5 designation means that the cloud environment is suitable for the most sensitive unclassified and classified information, including national security data.

One of the key benefits of the Office 365 Secret Cloud is that it enables collaboration and communication between different national security agencies. With traditional communication methods, it can be difficult to share information between agencies due to security concerns and restrictions. The Office 365 Secret Cloud allows authorized personnel from different agencies to securely collaborate and communicate in real-time, making it easier to share information and coordinate efforts.

The Office 365 Secret Cloud also provides a range of security features to protect classified information. These include multi-factor authentication, encryption at rest and in transit, and threat detection and response capabilities. In addition, Microsoft employs a dedicated team of security experts who monitor the environment 24/7 and respond to any security incidents that may occur.

The availability of the Office 365 Secret Cloud for US National Security Missions is a significant milestone for Microsoft and for the national security community. It demonstrates Microsoft’s commitment to providing secure and compliant cloud solutions for the most sensitive workloads, and it enables national security agencies to work more efficiently and effectively by providing a secure environment for collaboration and communication.

In conclusion, the Office 365 Secret Cloud is a game-changer for US National Security Missions. It provides a secure and compliant cloud environment for classified communications and collaboration, enabling national security agencies to work more efficiently and effectively. With the Office 365 Secret Cloud, authorized personnel from different agencies can securely collaborate and communicate in real-time, making it easier to share information and coordinate efforts. This capability is critical for protecting national security data from cyber threats and foreign adversaries.

Speak to an Engineer

To learn more or to start a project discussion – Request to speak to an Engineer.

_55b86715-32be-4623-924a-a83749dcac33

Microsoft Outlook is one of the most popular email clients used by millions of individuals and businesses worldwide and is the target of the latest Outlook Security Threat. It provides a user-friendly interface and advanced features for managing emails, calendars, tasks, and contacts. However, like any other software, Outlook is not immune to security vulnerabilities, and cybercriminals often target it to exploit such vulnerabilities for their nefarious activities.

Recently, Microsoft released a security advisory about a critical vulnerability that affects various versions of Microsoft Outlook on Windows and Mac operating systems. This vulnerability, tracked as CVE-2021-28482, is a remote code execution flaw that can enable an attacker to execute malicious code on the victim’s system by sending a specially crafted email to their Outlook account.

The vulnerability can be exploited when the user opens an email containing a specially crafted file that triggers the execution of the malicious code. Once executed, the attacker can take over the victim’s system, steal sensitive data, install malware, and carry out other cyber attacks.

To protect yourself from this vulnerability, it is essential to take the following steps:

  • Update your Outlook software immediately: Microsoft has released security patches for all affected versions of Outlook. Users should install the latest updates as soon as possible to prevent exploitation of the vulnerability. If you have enabled automatic updates, you may already have received the update. If not, check for updates and install them immediately.
  • Be cautious when opening emails from unknown senders or suspicious emails: To prevent exploitation of the vulnerability, it is crucial to be wary of any unsolicited emails or emails from unknown senders. If you receive an email from an unknown sender, do not open it and delete it immediately. If you receive an email with suspicious attachments, do not open the attachments or click on any links within the email.
  • Use antivirus software: Antivirus software can help prevent malicious code from executing on your system. It can detect and block malware and other cyber threats, including those that exploit vulnerabilities in Outlook.
  • Keep your operating system and other software up-to-date: Outdated software, including your operating system and other applications, can create security vulnerabilities that can be exploited by cybercriminals. Make sure to install updates regularly to keep your system secure.

In conclusion, the latest critical vulnerability in Microsoft Outlook highlights the importance of taking proactive steps to secure your system. By updating your software, being cautious when opening emails, using antivirus software, and keeping your operating system and other software up-to-date, you can help protect yourself and your data from cyber threats.

Exchnage_Powershell_Errors
Last reviewed: April 2026 — checked against current Microsoft product lifecycle and Exchange Online enforcement timelines.

If you are an Exchange Online administrator, you may have encountered a situation where the PowerShell cmdlets fail to execute. This issue can be frustrating, as it can lead to delays in critical tasks such as mailbox management, message tracking, and other essential Exchange Online operations. In this article, we will explore some of the reasons why Exchange Online PowerShell cmdlets fail and how to resolve them.

One of the most common reasons why Exchange Online PowerShell cmdlets fail is due to connectivity issues. The first step in resolving this issue is to ensure that your internet connection is stable and that you are not experiencing any network issues. If you are using a VPN connection, try disconnecting and reconnecting to the VPN to see if that resolves the issue.

Another reason why Exchange Online PowerShell cmdlets fail is due to authentication issues. This can occur if you are using an incorrect or expired credential. Ensure that the credential you are using is valid and has the necessary permissions to execute the cmdlet. If you are unsure, try running the cmdlet with elevated privileges.

Sometimes, PowerShell modules may not be loaded correctly, which can cause cmdlets to fail. To resolve this issue, try reloading the PowerShell modules by running the following cmdlet:

Import-Module ExchangeOnlineManagement

This cmdlet will reload the Exchange Online PowerShell module, and you should be able to execute the cmdlets without any issues.

In some cases, the issue may be related to the Exchange Online service itself. Microsoft periodically performs maintenance and updates to the service, which may result in cmdlets failing to execute. If you suspect that the issue is related to the Exchange Online service, try executing the cmdlet at a later time or contact Microsoft support for assistance.

In conclusion, Exchange Online PowerShell cmdlets can fail for various reasons, including connectivity issues, authentication issues, module loading issues, and Exchange Online service maintenance. By following the steps outlined above, you should be able to resolve most issues and execute PowerShell cmdlets successfully. If you continue to experience issues, reach out to Microsoft support for assistance.

Office 2013 EOL
Exchange2013EOL

On April 11th, 2023 support for Office and Exchange 2013 will no longer be available.


Microsoft products have a support lifecycle, also known as the Microsoft Lifecycle Policy. During a products lifecycle, they provide bug and security fixes. At the end of this lifecycle, the product reaches what is known as the end of support, and Microsoft no longer provides the following:

  • Technical support
  • Bug fixes
  • Security fixes

So What’s Next?

Depending on your situation, you can look in to the following options:

  • Upgrade your Outlook clients and / or servers to a newer version that is under current support from Microsoft – i.e. Office 2019.
  • If upgrading and you are not subscribed to O365 you can look in to licensing Office 2021 as a stand alone license.
  • If you need to migrate to Office 365 or consolidate Exchange server On-Premises, Priasoft offers the following solutions that will help you automate and speed up your migration process.

Public Folder Migration Manager.

Migrate public folders, permissions, and content.

Mailbox Migration Manager.

Migrate mailboxes, permissions, and content between Exchange and Office 365.

Collaboration Suite for Exchange.

Synchronize global address lists (GAL) for migration, mergers, or acquisitions.

Public Folder Analyzer.

Quickly report and analyze Public Folders, content, and permissions.

Migrate Public Folders
Last reviewed: April 2026 — checked against current Microsoft product lifecycle and Exchange Online enforcement timelines.

We have created a new comprehensive guide to migrating public folders to help those faced with such a project. The guide provides a detailed outline across 13 steps including undocumented quirks and challenges inherent with Microsoft Exchange Public Folders. The guide was born out of the past few years in which Priasoft Consulting Services led several very large projects from start to finish.

Recent activities with some very large customers, one with over 20 terabytes of data and more than 470,000 folders in the hierarchy, has given our team unique insight and experience that is now being shared so that others may achieve the same success.

Public Folders are just not a simple problem. They are complex regardless of total size and there are many oddities and idiosyncrasies that are rarely or never exposed or explained – by Microsoft or others. This guide tries to expose as much details as possible while at the same time presenting it in a way that can be understood.

The public folder migration guide can be reached at this URL: https://www.priasoft.com/docs/how-to-migrate-microsoft-exchange-public-folders/introduction/

Migrate Mailboxes to PST
Last reviewed: April 2026 — checked against current Microsoft product lifecycle and Exchange Online enforcement timelines.

This is one of the more common tasks for administrators and users alike. The need to export mail outside of the mailbox can stem from simple archiving to legal subpoenas.

In this example, we’ll show how to select several mailboxes from Microsoft Exchange, export the data, and some of the reporting that is available. Super-ExMerge, in contrast to the commands available on an exchange server such as New-MailboxExportRequest, Super-ExMerge does not run on the mail server. This means that the CPU demand for this work is also separated from the server. This can be valuable for cases where there may be concern about exporting a large quantity of mailboxes quickly. A Microsoft Exchange server is not going to allow “too much” to occur at the same time since it has to share the CPU between regular mail tasks and the export process.

The first step in this task is to identify all the mailboxes that need to be exported. Super-ExMerge uses Microsoft Exchange’s AutoDiscover feature to find and validate mailboxes to which to connect.

AutoDiscover accepts SMTP addresses for lookup requests. So, in this case we’ll need a list of email addresses for the mailboxes to be exported. If using Exchange 2007 or later, collecting email addresses for mailboxes is quite trivial using Exchange PowerShell:  

 

NOTE

Super-ExMerge uses MAPI to access mail data, not EWS (Exchange Web Services). This provides better performance and the ability to use multiple threads, and also better data fidelity since data stays in a native binary format thru the entire process.

$names = @('bruce wayne', 'alfred pennyworth', 'richard greyson', 'edward nygma')
$mbxs = $names | Get-Mailbox

Now that a list of mailboxes is found, we can build a set of connection objects that define our source and target stores for the export.

if (![System.IO.Directory]::Exists('c:\pstfiles')) { [System.IO.Directory]::CreateDirectory('c:\pstfiles') }
foreach ($mbx in $mbxs){
  $conn = New-ConnectionInfo Mailbox PST $mbx.PrimarySMTPAddress 'exch01.my-domain.com' 'admin@my-domain.com:Password' "c:\pstfiles\$($mbx.PrimarySmtpAddress).pst"
  $task = New-SyncTask $conn -OneWaySyncSourceToTarget
  Add-SyncTask $task
}

In the above script, we first make sure the destination for the PST files exists, and if not create it. The sync task won’t create the folder.

Next, we enumerate all the mailboxes collected earlier, creating a new connection object for each one. Note that some shorthand was used – the New-ConnectionInfo example doesn’t have any parameter names. All the parameters of that cmdlet are positional parameters, so if you set all the data in order on the command line, PowerShell will line up your arguments to the matching parameters.

We chose to use the email address of each mailbox as the name for our PST files. A “double quote” around text allows PowerShell replace tokens in the string with values. However, because $mbx is an object, if we don’t do some extra stuff, PowerShell will simple try to replace only the $mbx token with a string, followed by .PrimarySmtpAddress. The $(expression) syntax ensures that PowerShell evaluates the expression first, then converts that result to a string.

Once we have the $conn object created, we use it to create the $task object, specifying that it will be a one-way sync, from the source mailbox to the PST. Having been added to the task queue, the task engine will start processing the tasks. One question that will immediately arise is “how to I check on this?” Checking on running tasks is easy, as follows:

Show-SyncTaskProgress
TaskID                         : 335d55d1-1fc2-4f57-bc23-71c8319fa84d
TaskName                       : Sync from [Mailbox] bruce.wayne@wayne-enterprises.com to [PST] c:\pstfiles\bruce.wayne@wayne-enterprises.com.pst
------------------------------ :
Startup Progress               : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Source Folder Enumeration      : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Target Folder Enumeration      : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Source Folder Analysis         : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Target Folder Analysis         : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Source Items Enumerated        : [oooooooo                                                                        ]
Target Items Enumerated        : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Source Item Analysis           : [oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]
Target Item Analysis           : [                                                                                ]
Source Folder Content Collect  : [ooooooooooooooooooooooooooooooooooooooooooo                                     ]
Target Folder Content Collect  : [oooooooooooooooooooooooooooooooooooooooooooooooooooo                            ]
Item Processing                : [                                                                                ]
Item Completion                : [                                                                                ]
NOTE:

When Super-ExMerge is processing, the items and folders are discovered in separate threads. As such, progress is non-linear, meaning that many, if not all, of the progress bars will show increases as time proceeds. For example, the Items Completed may show 100% in one moment, but then show 20% in another because a different thread that is processing folders discovers more items.

We can see from the above that progress is being made on the export process. Given the performance-oriented nature of Super-ExMerge by the use of many independent threads, an ‘overall progress’ is not exactly easy to show. Once the enumeration and analysis progress bars show 100%, the Item Completion progress bar can be used as an overall progress indicator.  

Mail-Enabled-Public-Folder-Management
Last reviewed: April 2026 — checked against current Microsoft product lifecycle and Exchange Online enforcement timelines.

Introduction

When attempting to manage mail-enabled public folders many points of friction or frustration can occur.   Most of these points of pain come from the fact that the mail-enabled aspect of a public folder is a separated object from the folder in the hierarchy and the Active Directory proxy object does not store the folder path of the related folder in the hierarchy. The relationship between the proxy object and the folder in the hierarchy can be broken and happens whenever the directory ‘ObjectGuid’ does not match the value stored on the PR_PF_PROXY value of the hierarchy folder.   This break in the relationship can occur for many reasons:
  • The proxy object was somehow deleted and recreated which causes the object to receive a new ObjectGuid, and which now doesn’t match the hierarchy folder’s value.
  • The hierarchy folder loses the linking value thru some odd user interaction or by a replication failure.
  • The public folder in the hierarchy is moved to a new replica or public-folder-mailbox.   When a public folder is moved to a different ‘store’ (database or mailbox) its underlying EntryID value will change slightly as a result which can break the mail delivery since the AD proxy object had previously stored the value.
  • The public folder in hierarchy can be deleted and fail to delete the AD proxy object. This leaves behind an orphaned object in Active Directory and in the Global Address List.

When attempting to manage mail-enabled public folders many points of friction or frustration can occur.

Much of the management issue with public folder links comes from the carrying forward of older mail-enabled public folders from prior versions of Microsoft Exchange.   This is very prevalent if an organization’s mail system has existed since Exchange 2000 or 2003. In these older versions of Exchange EVERY new folder created was automatically mail-enabled but was hidden from the GAL.   When upgrading Exchange over the years many of these may simply have “come along for the ride”.   They will appear as mail-enabled folders from a management perspective, but in reality do not actually deliver mail because the mapi EntryID link format is incompatible with later versions of Exchange. We have published a detailed document, The Secret Challenges of Mail-Enabled Public Folders in Microsoft Exchange, on this subject as well as provide some recommendations as to how to detect and solve this issue. To learn more, Click Here
Exchange Server Hacker
Cyberespionage group, Turla, has reportedly developed a sophisticated Microsoft Exchange server backdoor that can redirect, intercept and modify email that is believed to have been in use since 2014. In addition, the exploit can also send messages on behalf of the compromised servers. According to the ESET report, LightNeuron has two main components: a Transport Agent, registered in the Microsoft Exchange configuration, and a DLL with most of the malicious code. Administrative privileges are required to drop the required files onto the Microsoft Exchange server before execution. Once successfully executed, the hackers that installed the backdoor can issue orders using JPG or PDF attachments with commands embedded via steganography. To learn more, see the detailed ESET report.