Overview

Microsoft is implementing size and count limits for various Exchange properties in two phases between September and November 2024. Microsoft has not provided a definitive date for either phase.

Exceeding these limits causes provisioning failures in Okta. Administrators must ensure that the specified attributes do not exceed the new limits to maintain service continuity.

When an attribute exceeds the limit, Okta displays the following error message in the Microsoft Office 365 application:

errorCode=ExceededAllowedLength; errorDescription=Unable to update this object in Azure Active Directory because the attribute [MSExchArchiveName] in the local Directory exceeds the maximum allowed length. To resolve this, reduce the length of the attribute in the local directory services and try again.

Applies To

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Microsoft Office 365 Application
• Microsoft Exchange Properties

Cause

Microsoft is changing the allowed size and count of values for various Exchange properties. Updating properties that exceed the maximum length (size of each value) or maximum count (total count of values) leads to service disruption.

Solution

How are the Microsoft Exchange property limits resolved?

Administrators must ensure that the attributes do not exceed the specified limits to prevent provisioning failures.

NOTE: If multiple attributes exceed the size limit, Microsoft only sends an error message for one attribute at a time.

Review the Phase 1 limits implemented starting in late September 2024 to ensure attributes comply with the new maximum length and count restrictions.

Review the Phase 2 limits implemented starting in late November 2024 to ensure attributes comply with the new maximum length and count restrictions.