Skip to content

Dashboard

The dashboard is the primary interface for Acmebot. The Function App serves it and it calls the same-origin /api/* endpoints.

Access

The dashboard requires authenticated requests, so configure App Service Authentication on the Function App before using it. Once authentication is enabled, open the Function App URL in a browser. If the dashboard returns 401 Unauthorized, check the authentication configuration first.

Certificate List

The dashboard lists certificates from the configured Key Vault and marks each one by category:

  • Managed by Acmebot and issued for the current ACME endpoint.
  • Managed by Acmebot but issued for another ACME endpoint.
  • Not managed by Acmebot.

Only certificates with Acmebot metadata for the current endpoint are selected for scheduled renewal.

DNS Zone List

The dashboard lists zones from all configured DNS providers. A provider that fails to list zones is dropped from the result, so check Application Insights if an expected provider is missing.

Load the zone list before issuing your first certificate. It confirms that DNS credentials, managed identity permissions, and network access all work.

Issue a Certificate

  1. Select a DNS provider and zone.
  2. Enter the record name under that zone.
  3. Review the resulting DNS name.
  4. Choose key options.
  5. Optionally set advanced options.
  6. Submit the request and wait for the operation overlay to complete.

Leave the record name empty for the zone apex, or use * as the leftmost label for a wildcard certificate.

Key Options

Key typeSupported values
RSA2048, 3072, 4096
ECP-256, P-384, P-521, P-256K

The default is RSA 2048. Use EC only when the downstream service supports the selected curve.

Advanced Options

Certificate Name

Certificate names can contain letters, numbers, and hyphens. If omitted, Acmebot derives a name from the first DNS name by replacing * with wildcard and dots with hyphens.

DNS Alias

Set DNS Alias when the ACME challenge should be created under another domain. Acmebot then validates through _acme-challenge.<dnsAlias>. This is useful when you delegate validation to a separate zone; ensure the required CNAME or delegation exists before submitting.

Tags

Custom tags are written to the Key Vault certificate. The Acmebot tag is reserved for internal metadata and cannot be set manually.

Renew a Certificate

Manual renewal reuses the existing Key Vault certificate policy and starts a new issuance orchestration. Use it to rotate a certificate before its scheduled renewal window.

Scheduled renewals run daily and add a random delay of up to 600 seconds before processing due certificates.

Revoke a Certificate

Revocation sends the certificate to the configured ACME CA's revoke endpoint. It does not delete the Key Vault certificate. After revocation, decide whether to delete, disable, or replace the certificate version according to your operational policy.

Operation Status

Issue and renew operations return an operation URL, which the dashboard polls until it completes or fails. If an operation fails:

  • Read the displayed problem message.
  • Check Application Insights for the orchestration instance ID.
  • Verify DNS records and provider permissions.
  • Retry after fixing the underlying issue.

Released under the Apache License 2.0.