Skip to main content
Complete installation and authentication first.

​
Choose a project interactively

At a terminal, run:
Enter a profile name, review the connection settings, and complete sign-in. Choose an organization and project from the numbered lists of names, then confirm the summary. Setup saves and activates the profile after confirmation; IDs are displayed only to distinguish entries. Cancelling, empty results, or an authentication/API error leaves the saved configuration unchanged. Setup makes service reads only. It requires an interactive terminal and rejects JSON output and root --query before sign-in or network access. For agents or scripts, use the manual commands below.

​
Use your saved context

Check the profile, organization and project shown here. Once they are saved, everyday commands use that context automatically:
You do not need to repeat --profile, --org-id, --project-id, or --json on these commands. Normal output uses the default auto renderer. Environment overrides still take precedence over saved settings, so check the effective context before making changes.

​
Manual selection for scripts

For non-wizard setup, first prepare authentication using your deployment settings. Discover the choices:
Replace ORG_ID with an organization ID from the first result. Choose a project from the second result, then save both IDs:
context use checks access to the organization and project before saving them to the selected local profile. The options after context use are required for this one-time selection; they are not needed on each later command. context show also reports the service URL, audience, authentication mode and config path. A saved project does not imply current permission: service authorization still applies to every request.

​
Switch between saved profiles

To create or update a named profile interactively, run tp profile setup and enter its name. The wizard resolves connection defaults for that target profile, rather than copying the previously active profile. For offline connection settings, use tp --profile work configure, then select context with the manual commands above. For unattended configuration after discovery, save explicit IDs without prompts:
Use the intended prepared profile and connection settings. This saves local defaults without authenticating or checking service access. Later, switch to an existing saved profile such as work with:
Use tp profile list to see saved names and tp profile show to inspect the selected profile. Selecting a profile does not switch the signed-in Azure account.
Global options go before the command path. Use an override only when this invocation should differ from the active profile:
These overrides do not change the active profile or its saved context. context projects --org-id is a command-local discovery option, while the identically named root option overrides the invocation’s default context.Profile selection uses --profile, then THINKPLATFORM_PROFILE, then the active saved profile (or default). Individual settings use explicit flags, then environment settings, then the selected profile. See authentication for the full precedence table.
An abbreviated result is {"profile":"work","org_id":4,"project_id":18}. Use IDs from your own environment. This JSON flag is optional for normal terminal use; scripts that parse JSON should request it explicitly. See scripting and output.
If discovery fails, confirm the active profile and identity, then check access with your administrator. Do not guess IDs. See the command reference for all profile and context options.