Establish a controlled session and complete a first operation.

1. Prerequisites

Access requires an assigned username, an active role, an approved browser, and the registered second factor when the identity is privileged. Do not reuse another operator's session or transfer session cookies between devices.

2. Sign-in sequence

1. Open the canonical HTTPS origin and confirm the host is nodeblobstore.com.
2. Enter the assigned username and password. The response does not disclose which field failed.
3. When prompted, complete the five-minute verification challenge. A challenge is bound to its initiating source and is removed after success.
4. Confirm the displayed name, role, team, and production environment before acting.

3. Console navigation

The console is organized around service health, storage topology, data movement, operational response, governance, and administration. Search locates resources and pages; it does not bypass role checks. Status labels describe the displayed control record, not an external provider guarantee.

Overview

Service posture, traffic indicators, active incidents, and recent changes.

Data and movement

Data spaces, pipelines, transfers, retention, and route state.

Operations

Alerts, incidents, change requests, access reviews, and audit records.

Administration

Integration registry, personal notification settings, and access profile.

4. Complete a first operation

Begin with a read-only inspection. Open a regional or pipeline record, note its identifier and health, then correlate the page with the current status notice. If a mutation is authorized, use the smallest operation that satisfies the change and record the returned request ID.

Scope: one named resource · Authority: assigned role plus approved change · Evidence: request ID, resource ID, and UTC time · Rollback: documented before execution

A disabled control indicates either read-only access or an unsupported transition. Do not attempt to work around it with direct requests.

5. Evidence and handoff

For consequential activity retain the change ID, resource ID, request ID, actor, UTC time, expected state, observed state, and reviewer. Never paste credentials, cookies, MFA values, connector secrets, or private endpoint material into a handoff.

6. Troubleshooting