Configure public access

Use this procedure only when the deployment outputs identify public service URLs and your security policy permits public access.

Before you begin

Obtain from deployment details:

• every public service hostname;
• the authoritative DNS target or records requested by the deployment;
• certificate status;
• any approved source restrictions.

Do not invent an IP address or infer a target from an internal Azure resource.

Configure and verify DNS

1. Ask the authoritative DNS owner to create exactly the records supplied by the deployment.
2. Wait for the record's configured DNS time to live.

3. From an approved client, query each hostname:

   nslookup <service-hostname>
   

4. Confirm the answer matches the authoritative deployment target.

5. Open the Kibana URL by hostname and confirm that the browser trusts the certificate.

6. Test the Elasticsearch URL without placing credentials on the command line:

   curl --fail-with-body --user "<user>" \
     "https://<elasticsearch-hostname>/"
   

   Enter the password when prompted by the client or use an organization- approved secret mechanism.

Safe result

DNS resolves consistently, TLS has no hostname or trust error, and the service returns an authentication response or authenticated product response.

If the hostname does not resolve, verify the authoritative record. If it resolves but the connection fails, follow connectivity troubleshooting.