2AYE
Guides, reference & supportCapability status

Support guidance

Administrator support

Find the failing boundary, preserve evidence and choose a safe next step for your organization.

Confirm the organization boundary

Check the active tenant, intended administrator role and the server’s next required setup step. Mailbox verification, company review, subscription status and permission to execute an action are separate checks. An administrator role alone does not activate a company.

Review Organization

Troubleshoot authentication

Confirm the configured identity provider, relying-party origin and allowed authentication methods before changing policy. Use the existing enrolled-factor recovery path for password resets where eligible. All-factor-loss recovery and identity-provider recovery require their own supported operator path; do not lower assurance to make a request succeed.

Open account troubleshooting

Locate the failing execution boundary

Trace the exact action across evaluation, approval when required, grant, redemption, destination outcome and receipt. Keep the original parameter spelling and action identity. A successful HTTP response or ALLOW decision does not establish that the destination committed an effect.

  1. Check tenant, issuer, destination, expiry and exact action bindings.
  2. Exercise refusal paths as well as a legitimate action using valid unspent authority.
  3. For uncertain outcomes, read destination state before retrying.
Inspect documented failure states

Preserve evidence and contain safely

Keep the relevant decision and receipt identifiers, timestamps and sanitized errors. Follow your authorized incident procedure to pause authority or revoke affected access. Do not share full audit exports, credentials or customer records in public channels.

Open Console evidence

Choose the right escalation

Use support for configuration and operational questions. Report a suspected vulnerability through the confidential disclosure channel. Include the environment and a sanitized reproduction; never publish exploit details or bypass a control as a workaround.

Read disclosure guidance