Can PnP Provisioning preserve SharePoint List GUIDs across environments?

Different GUIDs are expected because the target list is created as a new object. A list identifier is assigned to each list in its site collection, and the current PnP ListInstance schema has no supported property for supplying the source SPList.Id. The engine can register a ListId token only after SharePoint creates the list and returns its identifier. Documentation does not establish that older provisioning-schema versions supported forcing the original GUID, so legacy farm-schema examples should not be applied to SharePoint Online. Design dependencies around the list URL, title, or provisioning tokens where possible. For configuration requiring a GUID, resolve the new list after provisioning and update that configuration afterward. If an application has the source GUID hard-coded and cannot be changed, recreating the list is incompatible with that dependency. Preserving the site or redesigning the integration is safer than attempting an unsupported ID override.