Docs menu

Cloud

Goal: Know what each Cloud window sets up, what it needs first, and where the other windows are.

Every window on these pages opens as a panel: it floats at the right at first, docks anywhere, and keeps your place when you move it. See Node editors and work windows as panels.

The Cloud menu in the top bar is where a workspace gets its own place in Azure. Each item opens a window that sets up one thing in your Azure subscription. Those windows are not the canvas: each acts with its own button, not the canvas Save - Save & Provision in Data Fabric and Data Stores, Save configuration in Provenance, Connect Subscription in Cloud Connections, Provision Landing Zone in Landing Zone (each window's button is listed below). That button acts straight away; it does not wait for Deploy.

The order things unlock in

The Cloud items unlock in a fixed order. An item that is not available yet is left out of the menu, not greyed out.

The menu groups its items under three headings, Foundation, Data and Integrations, with a line between groups. A group whose items are all still locked is left out, heading and all.

GroupMenu itemStepShows when
FoundationCloud Connections1Always
FoundationLanding Zone2The workspace has a connected cloud
FoundationDNS & Domains3A connected cloud and a provisioned private landing zone
FoundationApp Identity3The same
DataData Stores3The same
DataData Fabric3The same
DataProvenance3The same
IntegrationsCommunications3The same
IntegrationsSource Control3The same
IntegrationsOEM Integrations3Turned off for now; when it returns, the same and the Workspace.Experimental right

The menu lists them in that order. Landing Zone needs only the cloud, because it is the window that creates the landing zone.

What "connected" and "provisioned" mean

Both are read from what the workspace has stored, never by asking Azure, so the menu does not depend on a network call:

  • A connected cloud is a stored cloud connection whose application id, secret, subscription id and tenant id are all filled in. A managed subscription counts once it is set up and those four are filled in.
  • A provisioned landing zone is a stored landing zone whose region, resource group, storage account and Key Vault are all recorded. Log Analytics and Application Insights are optional and do not count.

When something is not available yet

The menu hides such a window, but a request for a kind that needs the landing zone - through the API, over MCP, or as a proposal - is answered with the code PRIVATE_LANDING_ZONE_REQUIRED and the sentence "This needs a private landing zone, which this workspace does not have yet." The next step it names depends on what is missing: with no connected cloud, connect a cloud from Cloud -> Cloud Connections, then create the landing zone from Cloud -> Landing Zone; with a cloud, only the second.

An AI connected over MCP sees the same chain. get_workspace lists each kind that is not active yet under Capabilities.InactiveKinds, with its code, reason, next step and Requires - the record kinds still missing, in setup order (for example Clouds, then CALZ).

The badges on the menu

A number on an item means something there is waiting for you. The closed Cloud menu shows the sum.

ItemCounts
Cloud ConnectionsStored clouds whose credential is close to expiry or expired, plus pending Cloud proposals
Landing ZonePending landing zone proposals
Data FabricPending proposals, a stopped cluster, a hub at 80% or more of today's message quota, and each setup piece left unfinished
Data StoresPending account proposals
ProvenancePending Provenance proposals
Source ControlPending connection proposals and connections needing attention
App IdentityPending access-right and access-configuration proposals

Communications and OEM Integrations carry no badge.

The windows

WindowSets upIts button
Cloud ConnectionsThe Azure subscription your workspace runs inConnect Subscription, Create Subscription, or the managed subscription's Yes, create the subscription
Landing ZoneYour private landing zone: a resource group, storage and a Key Vault of your ownProvision Landing Zone
Data FabricWhere device data arrives and is stored and queriedSave & Provision
Data StoresCosmosDB accounts for documentsSave & Provision
OEM IntegrationsA preview with sample dataNone
ProvenanceThe record of changes, its retention and signingSave configuration
App IdentitySign-in for the apps you deploy, and the access rights they useSave Provider, and Save on its other tabs
Source ControlThe GitHub organisations your code lives inConnect GitHub, then Accept connection and the steps on GitHub
CommunicationsThe mail accounts your workspace sends and reads email throughConnect your first mail account, then Save account
DeployOpened from Deploy in the top bar: builds and removes what you savedDeploy

TIP

Most setup windows build Azure resources when you press their button, and those bill to your Azure subscription. Save account in Communications builds nothing: it stores the account's settings and puts its password or secret in your Key Vault. Canvas changes are different: they are built by Deploy. See Save, accept and Deploy.

Everything these windows and Deploy build sends its logs to your landing zone. What it sends, and the switches that set it, are in Logging.

When a setup or a deploy ends

Some setups take a long time: the Data Fabric's analytics server can take up to an hour. You don't have to keep its window open, or even the tab it started in. When a setup or a deploy ends, every OpenX tab open on that workspace shows a short notice in its corner: "Data Fabric is ready.", "Deploy finished.", or, when it failed, the run's own reason, for example "Data Fabric failed: Azure had no room for that size." That includes a teammate's tab.

  • Open <window> on the notice opens that run's window.
  • × puts the notice away.
  • The Deploy and recent activity icon in the top bar keeps a violet dot until you open it (or follow the notice's link). Its title says how many runs ended since you last looked.

Each tab keeps its own dot: opening the activity in one tab does not clear another. A run that ended before you opened the tab is not announced again. A canvas Save is not a setup, so it raises no notice. When a run ends, every open tab also reads the workspace again, so the Deploy window's next step and the windows' records are what the run left. A tab you are not looking at catches up when you come back to it. There is no browser pop-up and no email.

Proposals in the Cloud windows

Thinky and agents can propose most Cloud records; a person accepts. Any workspace member can accept a proposal; some changes (access, licenses, connected-app requests) need a management right. Accepting writes the record to the workspace; the window's own button, or Deploy, is what builds it in Azure. Each window's page says what can be proposed there and where you accept it. In Greenfield, Thinky's own proposals are accepted for you; the window's button or Deploy still does the building.

Thinky, or an agent connected over MCP, can propose a cloud connection and, once a cloud is connected, a landing zone. A proposal never carries a credential (CREDENTIAL_IN_PROPOSAL). Proposing is not connecting or creating: a person accepts in the window, by doing their part there. In Cloud Connections the proposal shows over the normal Connect form, filled from it, and Accept proposal and Connect accepts it, then connects with what the form holds; a cloud proposal accepted anywhere else is saved, not connected, until the person connects it there. Accept Proposal and Create in Landing Zone records it, then starts the window's own create. In Greenfield, Thinky's own cloud connection or landing zone proposal is accepted for you, which only records it; Thinky then names the window where you connect or create it.

The kinds that need the landing zone (Provenance, IoT, Data Stores, Communications, App Identity, Source Control) can be proposed only once the cloud is really connected and the landing zone created. Until then get_workspace lists them under InactiveKinds with Requires, and a proposal for one, even in the same bundle as the cloud connection or landing zone, is refused PRIVATE_LANDING_ZONE_REQUIRED: a proposal cannot connect or create.

Other windows

Menu or placeWindow
Workspace -> SettingsWorkspace Settings
Workspace -> Team MembersTeam Members
Workspace -> AlertingAlerting
Workspace -> View All...Manage Workspaces
Workspace -> Manage Fathym WorkspaceManage Fathym Workspace
fAI -> Manage Remote ConnectionfAI Remote Connection
APIs -> API KeysAPI Keys
APIs -> API ManagerAPI Manager
APIs -> OpenX MCP ServerMCP Server
Licenses -> Manage LicensesLicenses
Billing -> Current LicenseCurrent License
Manage Profile in the top barAccount Profile

Next steps

On fathym.com: OpenX →

On this page