/ Docs
Meta

Troubleshooting

This page provides solutions for common issues when using Impliancy.

This page provides solutions for common issues when using Impliancy.


Inventory issues

An environment is marked as "missing permissions"

This means the service principal does not have the System Administrator role in the environment.

Fix: As an admin, click on Dashboard and then on Grant Access. That should automatically add the "App Impliancy" to all environments as System Administrator.

Alternatively, you can do this manually, by:

  1. Go to Power Platform Admin Center
  2. Open the environment
  3. Assign System Administrator to the "App Impliancy" service principal
  4. Wait a while for the Impliancy app to do the inventory sync job

Artifacts are missing or outdated

The environment may be:

  • Excluded from inventory
  • Missing permissions
  • Not synced recently

Fix:

  • Ensure environment inventory is enabled
  • Confirm service principal permissions
  • Wait for the next background sync or trigger a manual sync

Compliance issues

My compliance form does not appear

Possible causes:

  • Compliance is disabled for the environment
  • A form is not configured for that artifact type
  • The artifact already has a valid, non-expired submission

Fix:

  • Check environment settings
  • Ask your admin to verify form setup

Inactivity issues

I received an inactivity notification, but the artifact is still used

Impliancy tracks last modified / last run.
If you triggered the artifact recently, the next sync will update the activity status.

Fix:

  • Wait for the next sync
  • If necessary, manually trigger the artifact again

Ownership issues

I cannot change the owner of an artifact

Only admins and current owners/deputies can change ownership. Given that:

  • Owner must exist in the Power Platform
  • The app must not be a system app

Login issues

I cannot sign in to Impliancy

Check the following:

  • Your user exists in the tenant connected to Impliancy
  • Conditional Access or MFA policies do not block the login
  • The enterprise application was not removed accidentally