Target Tenant Resource

A Target Tenant Resource is an application object that receives configuration updates when a global package is imported into a destination tenant.

The resource becomes the deployment target for package content. For the full list of supported resources, see Target tenant editable resources.

During package import, the system evaluates whether a corresponding resource already exists in the target tenant. The matching process determines whether the resource will be created, updated, skipped, or will generate a validation error. The matching process occurs when you use resource identifier, internal GUID, or package metadata reference.

Target tenant resource states

A target tenant resources can be divided according to these states:

  • Resource does not exist.
  • Resource exists and is editable.
  • Resource exists with local modifications.
  • Resource is removed from the source package.

If the target resource does not exist:

  • A new resource is created.
  • Package values are applied.
  • The resource becomes managed by the package.

For example, if the source tenant contains a security role named AP Administrator and the role doesn't exist in the target tenant, the role is therefore created.

If the target resource already exists and supports updates:

  • Package changes are applied.
  • Existing values may be updated.
  • Resource remains synchronized with package content.
For example, if the package contains updated permissions for AP Administrator role and the role already exists in the target tenant, then permission changes are applied and the existing role remains available.

If target tenants have locally modified resources, a behavior depends on package rules. These are the possible outcomes:

  • Package replaces local configuration.
  • Package preserves local overrides.
  • Conflict resolution occurs during import.

Import behavior depends on configured package ownership and synchronization rules.

When a resource is removed from the source package, these are the possible outcomes:

  • Resource remains in target tenant.
  • Resource becomes unmanaged.
  • Resource removal is offered as an import action.

This behavior depends on package lifecycle management policies.