Splunk Cloud Administrators, Identity & Access Engineers
When linking a Splunk Cloud Platform stack to a Splunk Observability Cloud organization (via the Splunk App for Observability Cloud setup page), the integration status may report as Active with configuration type Unified Identity, but the required Observability capabilities and default o11y_* roles (such as o11y_access and o11y_admin) fail to populate on the Splunk Cloud stack.
In environments where corporate policy prohibits installing the acs binary/CLI, administrators must execute capability enablement directly against the Admin Config Service (ACS) REST API.
mycompany).sc_admin role on the target Splunk Cloud stack.Define your stack parameters and credentials in your terminal session:
export SPLUNK_STACK="<your-stack-name>"
export ACS_TOKEN="<your-jwt-or-bearer-token>"
export ACS_BASE_URL="https://admin.splunk.com/${SPLUNK_STACK}/adminconfig/v2"
Verify the current state of enabled features and capabilities to confirm missing Observability entitlements:
curl -s -X GET "${ACS_BASE_URL}/capabilities" \
-H "Authorization: Bearer ${ACS_TOKEN}" \
-H "Content-Type: application/json" | jq .
Send a POST request to register and activate the Observability Cloud capabilities on your stack:
curl -X POST "${ACS_BASE_URL}/capabilities" \
-H "Authorization: Bearer ${ACS_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"name": "o11y_access",
"action": "enable"
}'
Unified Identity: Splunk Cloud Platform and Splunk Observability Cloud
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |