Holds: Couldn't update the following event error when editing calendar items from OWA or Outlook

By Ashwin Venugopal -

 





Symptoms

The following scenarios might happen:
  • A user is a mailbox in Microsoft 365.
  • In-place hold or litigation hold is enabled for the mailbox. 
  • The user tries to edit calendar items from Microsoft Outlook Web App (OWA) or Microsoft Outlook. 

In these scenarios, the user receives the following error message:

Couldn't update the following event-
<EventName>

Cause

This issue occurs because the Versions folder (that is part of the Recoverable Items folder) is full. To check the Recoverable Items folder statistics-

Get-MailboxFolderStatistics -Identity cloudtest -FolderScope recoverableitems  | ft name, *size*

Resolution

Since the user's mailbox is currently on hold, the contents of the Versions folder hold great significance. To address this situation, it is necessary to activate the archive mailbox for the user in question, and subsequently transfer all items from the Versions folder into the archive mailbox. To do this, follow these steps:
  1. Enable the archive mailbox via Enable-Mailbox -IdentifyUserName-Archive command.
  2. Turn on the auto-expanding archiving feature through Enable-Mailbox <UserMailbox> -AutoExpandingArchive.
  3. Create a custom retention policy for mailboxes on hold, and then move the items from the Versions folder to the archive mailbox.

More Information

When a user's mailbox is under in-place hold or litigation hold, both the original items and any modified items are duplicated to the Versions folder. If the Versions folder reaches its capacity, the modified version of the original items cannot be saved in the folder. Consequently, the user is unable to save modifications to the original items. 

Conclusion

The error has been resolved with the help of above methods. 
































































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can...
Read more