Feature Request:
Enhance RingCentral Active Directory/SCIM user provisioning to support clearing or removing an existing user attribute in RingCentral when the corresponding attribute is blank or removed in Azure AD/Entra ID or Okta.

Current Behavior:
When an attribute, such as a mobile phone number, is cleared or left blank in Azure AD/Entra ID or Okta, the identity provider may not explicitly send an API request setting the attribute to an empty value. As a result, the existing value remains populated in RingCentral.

This appears to be a common limitation with both Azure AD/Entra ID and Okta, where an empty attribute is not necessarily transmitted as an explicit empty value through the provisioning API.

Requested Enhancement:
Allow RingCentral Active Directory/SCIM provisioning to recognize when a previously populated attribute is removed or becomes empty in the identity provider and automatically clear the corresponding value in RingCentral.

Use Case:
Administrators need a reliable way to keep RingCentral user profiles synchronized with their identity provider. For example, if a user's mobile number is removed from Azure AD/Entra ID or Okta, the existing mobile number should also be removed from the user's RingCentral profile instead of remaining populated.

Business Impact:
Without this functionality, administrators may need to temporarily disable SCIM provisioning and manually clear affected attributes in RingCentral, which creates additional administrative overhead and can result in stale user information.