So you can't manage or delete the object from the on-premises environment.
The on-premises AD DS is no longer available. This issue may occur if one or more of the following conditions are true: In this scenario, you can't remove the orphaned user account by using the Microsoft cloud service portal in Office 365, Azure, or Microsoft Intune, or by using Windows PowerShell. You try to manually manage or remove objects that were created through directory synchronization from Azure Active Directory (Azure AD):įor example, you want to remove an orphaned user account that was synced to Azure AD from your on-premises Active Directory Domain Services (AD DS). Original product version: Cloud Services (Web roles/Worker roles), Azure Active Directory, Microsoft Intune, Azure Backup, Office 365 Identity Management Original KB number: 2619062 Symptoms It provides two resolutions for this issue according to different reasons. For example, a dependent value is only available if it’s available in the selected record type and the selected controlling value.This article describes an issue that you can't manage or remove objects that were created through directory synchronization from Azure AD. The record type and the controlling field together determine what values are available in the dependent picklist. If your org uses record types, choose a record type to test how it affects your controlling and dependent picklist values. 
You can set default values for controlling fields but not for dependent picklists.Multi-select picklist fields can be dependent, but not controlling fields.Standard picklist fields can be controlling fields, but not dependent fields.Custom picklist fields can be either controlling or dependent fields.Optionally, click Preview to test your selections.Use the field dependency matrix to specify which dependent picklist values are available when a user selects each controlling field value.Choose a controlling field and dependent field.From the management settings for the object you want to add a field to, click Fields & Relationships.
0 kommentar(er)
