Skip to main content

User Onboarding

User onboarding is complete when you can sign in, verify the right tenant and project, protect your account, launch an approved runtime, connect to it, and release it when you are done.

First 30 Minutes

TimeActionStop if
0-5 minSign in and confirm the tenant and project shown in the top bar.The tenant or project is missing or unexpected.
5-10 minOpen account security and review MFA, SSH keys, API keys, and sessions.Account protection is required but no setup or recovery path is visible.
10-15 minOpen Workloads, Compute, and Apps to see what you can launch.Catalog or capacity is empty without a clear reason.
15-25 minLaunch the approved compute or app runtime for your walkthrough.Launch fails without a visible next action or correlation ID.
25-30 minOpen the workload detail page and connect using the available action.The workload is active but no connect action works.

Account Readiness

Before running work, check:

  • Tenant and project: the top bar should show the workspace and project where you intend to spend capacity.
  • MFA: if required, complete setup before sensitive account changes.
  • SSH keys: add a public key if the workload needs SSH access.
  • API keys: use API keys only for automation that needs them.
  • Sessions: review active sessions and sign out stale sessions when needed.

Launch Readiness

You are ready to launch when the product shows:

  • a runtime or SKU you are allowed to use;
  • enough balance, entitlement, or quota for the request;
  • a compatible region and image;
  • the required access method, such as SSH key or browser terminal;
  • any storage dependency needed by the workload.

If Something Is Missing

Missing itemWho can help
Tenant or project accessTenant admin
Role or permissionTenant admin or project owner
Balance, quota, or entitlementTenant admin or billing owner
Capacity in the chosen SKU or regionTenant admin or platform support
MFA recovery or lost deviceTenant admin or account support

When asking for help, include the tenant, project, action attempted, visible state, and correlation ID. Do not include tokens, private keys, one-time codes, or secret values.

Next Step

After onboarding, continue to Launch And Operate.

For account protection details, see Account Security. For capacity, runtime, and storage terms, see Concepts and Runtime Families.