Skip to content

Review deployment outputs

Use the managed application's deployment details as the source of truth for resource IDs and endpoint names. Never reconstruct internal resource names from a naming convention.

Record the deployment identity

  1. In the Azure portal, open Managed applications.
  2. Select the deployed application.
  3. Record the subscription, application resource group, application resource ID, region, and provisioning state.
  4. Open the most recent successful deployment and review Outputs.
  5. Use the managed application view for supported customer-facing properties that are not exposed as ARM outputs.

Record connection information

Where present, record:

  • Elasticsearch URL;
  • Kibana URL;
  • Fleet and Logstash URLs if the selected plan exposes them;
  • whether each endpoint is public or private;
  • required service hostnames;
  • the authoritative Private Link Service resource ID;
  • any customer DNS action;
  • certificate or CSR status.

Outputs must not contain secret values. If an output appears to expose a password, token, private key, or connection string, do not copy it into documentation or a ticket. Report it through the approved security process.

Verify the outputs

  • Hostnames use the approved customer or managed domain.
  • Private endpoints are not expected to work before Private Endpoint, DNS, and TLS configuration is complete.
  • Public endpoints resolve to the expected public path and present a trusted certificate.
  • The recorded Private Link Service resource ID comes directly from deployment details.

Next, choose an access model.