Microsoft Dynamics 365 Backup and Restore Known Issues, and Limitations | Dell Technologies

Type (Ticket)	Description
Known Issue (INS-186566)	When a restore is initiated, the status may remain at 0% initially due to backend discovery for a few minutes. For long-running restore jobs, the status may inaccurately show 100% while the job is still in progress. This occurs because the total number of objects or records to be restored cannot always be determined upfront.
Restore Limitations	Certain internal entities, such as `system users`, `business units`, `organizations`, and `transaction currencies`, cannot be restored to a different environment. These entities are managed at the Entra ID, Power Platform, and Power Apps levels and fall outside the scope of Microsoft Dynamics 365. As a result, any references to these entities will not be included in the record restore process. If referenced entities or records do not exist in the destination environment, some entity restorations may fail. In such cases, the record itself will be created, but the missing references will not be restored. The Microsoft Dynamics 365 APIs does not support partial reference restoration. This means that either all references associated with a record will be restored successfully, or none will be attached.
Known Issue	Display of Primary Name in Record Listing for Internal Entities Certain internal entities in Microsoft Dynamics 365, such as `activityparty`, have a `primaryKey` defined in metadata but not in actual data. As a result: The name column may appear in the record listing, but its value will be empty because Microsoft does not return this data. This occurs because these columns are internally managed and read-only within Dynamics 365, with their connections varying across different entities. Customers cannot create data for these internal entities from the Dynamics 365 portal. Therefore, on the UI, the value will appear as null for these entities.