Fathym
Menu
fAIOpenXThe LoopHolonicAboutDocsBlogLog in to OpenX
Docs menu

get_azure_listing

This page answers what get_azure_listing returns, what it takes, and what happens when the person has not signed in to Azure yet.

Purpose

get_azure_listing shows an AI the person's Azure directories, subscriptions and billing scopes for this workspace, as names and codes (tnt-, sub- and bil- codes). It never returns an id or a token. The AI uses the codes in a Cloud proposal, only while the Cloud is not connected: SubscriptionID and TenantID for an existing subscription, or BillingScope (and no SubscriptionID) for a new one. In Cloud Connections the proposal shows over the normal Connect form, where each code becomes the person's own id and they can change any field. "Accept proposal and Connect" accepts the proposal, then connects.

It tells the client it is read-only. A listing lasts 15 minutes.

Inputs

It takes no inputs. The workspace and the person come from the connection, so nothing an AI sends can point the listing at someone else's.

Example

{}

When a listing exists, the answer carries the directories, the subscriptions and the billing scopes, each with a Name and a Code.

When nothing is listed, the person signs in to Azure on the OpenX page, and the AI never sees an id or a token:

  • A client that supports URL mode gets the MCP error -32042 with the sign-in link, and opens it for the person.
  • Any other client gets the same link as text, in SignInUrl, with the code AZURE_SIGN_IN_NEEDED. Give it to the person to open in their browser.

After the person finishes, call the tool again. retrieve_inventory also carries the listing while a Cloud is not connected, but it only reads: it never sends the link.

Errors

  • AZURE_SIGN_IN_NEEDED: nothing is listed. The answer gives the sign-in link as SignInUrl. (A client with URL mode gets -32042 instead.)
  • AZURE_NOT_LISTED: shown by retrieve_inventory as the reason its AzureListing is Known: false, when the person has not signed in yet. Call get_azure_listing.
  • AZURE_LISTING_UNREACHABLE: the listing could not be reached. Ask again shortly.
  • AZURE_LISTING_REFUSED: the listing was refused, or the connection names no AI client. The answer carries a remedy; reconnect the AI client to OpenX if it says so.
  • AZURE_SIGN_IN_LINK_REFUSED: the sign-in link could not be created. Ask again shortly.
  • AZURE_SIGN_IN_LINK_UNSAFE: the link that came back was not one OpenX sends, so it is not passed on.
On this page