Virtual Machine provision request is failing with the error message "Failed to process the payload for : Azure_TF_Provision_Response_Processo"Issue Virtual Machine provision request is failing with the error message "Failed to process the payload for : Azure_TF_Provision_Response_Processo". When reviewing the Cloud Orchestration Trails [sn_cmp_cloud_trail] generated for the request item, we see the below error message that actuall caused the provision request to fail:Error Message: ["ABANDONEDAbandoned due to too many errors","INVALID_INPUT_DATAFound invalid sys_id in payload. No record with sys_id [XXXXXXXXXXXXXXXXXXX] exist in table [cmdb_ci_azure_datacenter] or is a duplicate record with [duplicate_of] field set to a master CI","INVALID_INPUT_DATAFound invalid sys_id in payload. No record with sys_id [XXXXXXXXXXXXXXXXXXX] exist in table [cmdb_ci_cloud_service_account] or is a duplicate record with [duplicate_of] field set to a master CI","ABANDONEDAbandoned due to too many errors","ABANDONEDAbandoned due to too many errors","ABANDONEDAbandoned due to too many errors"] ReleaseAllCauseThis issue occurs in the domain-separated instance, where the MID server user (sys_user) and the Mid server (ecc_agent) records are in the "Global" domain and trying to create the CIs in the CMDB in the child/leaf domains.ResolutionThe system property 'glide.ecc.enable_multidomain_mid' must be set to "true". If the goal is to allow MID servers in the "Global" domain to access multiple domains, you may apply the steps mentioned in the following documentation:https://docs.servicenow.com/bundle/xanadu-servicenow-platform/page/product/mid-server/concept/c_MIDServerDomainSeparation.html#configure-multi-domain-mid-server