Before you begin
Confirm account, tenant and active role in the account menu. Inspection requires view permission; changing records requires the specific management permission. A hidden or disabled action can reflect authorized scope; do not switch tenants to evade a denial. Work only with records in the workspace you are allowed to administer.
Procedure
- Open Registrations, find the request and inspect View details.
- For an eligible pending request, use Approve registration or the rejection action, verify the applicant and complete the required reason.
- Save and refresh the inventory before another decision.
Behavior and limits
Viewing requests and deciding them are separate permissions. The result records administrative review; tenant and user creation and readiness must be checked separately.
If another administrator already decided or the record changed, refresh and review its latest state. Do not announce an account is ready merely because the request is approved.
Inspect name, organization, type, received date and previous review. The reason should explain the decision without unnecessary data. A request that is no longer pending is not eligible for another ordinary decision.
Verify the result
After saving or confirming, reopen the detail and check the state reported by the server. Distinguish an accepted request from a completed operation and retain only minimal evidence without sensitive information. When an operation is pending, wait for its final state in the corresponding view before starting another action on the same object.
Laboratory example
Use the synthetic tenant documentation-lab and, where relevant, worker worker-demo-a. Note the previous state, perform one authorized action and compare the resulting state. These names illustrate the procedure; they do not identify production records or authorize creating cloud resources. For a review without changes, inspect the detail and cancel any open form.
If something fails
If a conflict appears, refresh the inventory and review current values before repeating. If the session expired, sign in and complete MFA when required. For a permission error, check the role and membership; for a provider error, inspect the operation and its safe message. Do not alter storage, revisions or controls to force an outcome.