A few days ago, I found an email in my my mailbox stating the below.

Dear Partner,

We are pleased to announce that the new patch P20231005 for Veeam® Backup for Microsoft 365 v7 is now available for download.

For partners using modern app‑only authentication, this build brings back the support for backup and restore of public folders and discovery search mailboxes, as well as identification of a shared mailbox user. (emphasis added)

Along with that, the patch delivers a set of bug fixes and resolves the memory leak issue observed in the earlier build relating to the use of the Exchange Online PowerShell module leveraged in some service operations (see more details in KB4481).

However, we would like to draw your attention to the fact that using the abovementioned PowerShell module may still cause a higher memory usage on hosts than it used to be on earlier product builds. To avoid any potential issues on your proxy hosts, we advise you to test this patch in an environment with a high load before applying it to your production.

Thank you,
Veeam Team

The beauty of this, is that a feature I was hoping to see in version 8 appears to have been added, that is, the ability to discern between user mailboxes and shared mailboxes when selecting what to backup. More testing is warranted, but if this is the case, I’m very excited for this very small feature add!

Update: I had intended on posting this last week but it sat in drafts, and in the meantime, the P20231005 (7.0.0.3968) patch was retracted “due to issues relating to Connect-ExchangeOnline and Disconnect-ExchangeOnline cmdlets” and a subsequent patch P20231005 (7.0.0.4385) was released, and just recently P20231015 (7.0.0.4388) was also released. The same KB4425 has the information for all. The post title above which originally cited P20231005 has been updated to P20231015 for accuracy as well.