Creating a Gateway Instance
Above the gateway table, a status-strip filter bar lets you switch the whole page between Live, Up to date, Pending, Pending + failed, Failed only, and Never published views. Five KPI cards summarize Runtimes (count and number of regions), Healthy (how many of the total are healthy vs. degraded), Active agents secured through Agent ID Secure, Requests in the last 24 hours (with day-over-day percent change), and Registered resources. The table lists the Gateway name, Environment, Deployment target (AWS, Azure, On-prem, Air-gapped, or Not specified), Status (Registered · not connected, Healthy, or Degraded), Identity provider (shows Not configured with a Configure link until one is set—see Connecting an Identity Provider to a Gateway), Last heartbeat (Never connected until theruntimeconnects), and a count of Pending change sets waiting to be published to that gateway.
Procedure
- On the Gateways page, click Create gateway.
In the New gateway instance dialog, provide a Display name for the gateway.
Optionally, enter an Environment label, for example, Production or APAC nonprod.
In the MCP Gateway Base URL field, enter the address that AI tools and MCP clients use to connect to the gateway, for example, https://mcp.example.com. Agent ID also uses this address for sign-in callbacks. You cannot change this address after you create the gateway.
Optionally, under Where will you deploy this?, select AWS, Azure, or Kubernetes.
Click Register.
Results
The Instance registered dialog opens with the status Registered · not yet connected. The instance record starts empty, with no agents, MCP servers, or policy rules inherited from the tenant. From this dialog, you can click Download bundle to download the runtime package, or click Done and download it later from the Actions menu. The new gateway appears in the gateway table with its Status column showing Registered · not connected until its runtime connects, and then Healthy once it does, and its Identity provider column showing Not configured until one is set (click Configure in that column) and resources are published to it.
Related Articles
Manually creating the node secret for RSA Authenticaiton Manager fails on Microsoft Forefront Threat Management Gateway 290Number of Views Connecting an Identity Provider to a Gateway 1Number of Views Registering a Resource Behind a Gateway 1Number of Views Change the Primary Instance IPv4 Network Settings 480Number of Views Installing the Gateway Runtime 2Number of Views