Azuredocs
Whitelist / Guide

Keys and sessions

Manage who can run a release and what happens when access changes.

Key lifecycle

Keys belong to an access policy, not a UI badge. Review the project, expiry, usage and device settings in the dashboard before issuing a key.

  1. 01
    Issue

    Create a test key under the intended project and script scope.

  2. 02
    Validate

    Run the generated integration with that key on the intended device.

  3. 03
    Revoke

    Disable access or end the session through the dashboard, then verify the client stops protected functionality.

Session behavior

  • Handle failed checks explicitly; stop gated actions rather than continuing on cached success.
  • Treat network failure separately from an invalid key in user feedback, but do not bypass authorization.
  • Use the reset controls provided by your project when a device binding must change.

Troubleshooting

For expired or device-bound keys, inspect the key in the dashboard. Regenerating unrelated credentials is not a fix for a policy mismatch.