Splunk Microsoft Cloud Setup

Microsoft Cloud Add-ons Setup (Office 365, Entra ID, Graph)

Prerequisites

Workflow Overview

┌───────────┐   ┌───────────────┐   ┌───────────────┐   ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘   └───────────────┘   └───────────────┘   └─────────────────┘

When to Activate

• Splunk_TA_o365, Office 365, Microsoft 365, Entra ID, Azure AD audit/sign-in, Microsoft Graph, Splunk Add-on for Microsoft Cloud Services, or Microsoft cloud log onboarding in Splunk.
• Preview and review the splunk microsoft cloud setup workflow before any live apply phase.
• Diagnose failed prerequisites, generated assets, configuration, or validation evidence.

Scope

Follow the documented read-only or render-first path whenever it is available. This skill does not imply permission to mutate live systems. Require explicit apply flags, protected credentials, and operator review for state changes.

Examples

Inspect the supported setup modes before selecting one:

bash skills/splunk-microsoft-cloud-setup/scripts/setup.sh --help

Expected output: usage, supported modes, and required arguments are displayed without changing the target environment.

Inspect validation modes before running completion checks:

bash skills/splunk-microsoft-cloud-setup/scripts/validate.sh --help

Expected output: offline, live, and completion options are displayed when the skill supports them; help exits without mutation.

Troubleshooting

TA Completion Gate

For every TA/add-on or dashboard companion run, satisfy the shared TA completion gate: configure and enable the data ingest path owned by this skill or its required companion, validate events or metrics in the target indexes/source types, and verify any pre-built/package-shipped dashboards are visible, macro-aligned, and returning data. If the package ships no dashboards, record that evidence explicitly and hand off dashboard use to the consuming app, ES/ITSI/ARI content, or readiness doctor.

Render-first automation for Microsoft cloud log onboarding through two real Splunk-supported add-ons:

• Splunk Add-on for Microsoft Office 365 (splunk_ta_o365, Splunkbase 4055) - Office 365 Management Activity (including Audit.AzureActiveDirectory), Microsoft Graph, Entra ID metadata, service status, and message trace.
• Splunk Add-on for Microsoft Cloud Services (Splunk_TA_microsoft-cloudservices, Splunkbase 3110) - Azure audit, storage, Event Hub, and resource data.

Both authenticate to Microsoft Entra ID (Azure AD) with an app registration. The add-ons run on the search tier or a dedicated heavy forwarder; they are not Universal-Forwarder safe.

Feeds

Credentials

Never paste the Entra client secret in chat or argv. Create an Azure app registration, then write the client secret to a local file and register it in each add-on's Configuration tab:

bash skills/shared/scripts/write_secret_file.sh /tmp/msentra_client_secret

See the rendered account-setup.md for the full app-registration runbook, required Graph / Office 365 Management API permissions, and the exact REST endpoints.

Workflow

1. Render reviewable assets (offline):

bash skills/splunk-microsoft-cloud-setup/scripts/setup.sh --render \
  --o365-index o365 --azure-index azure --tenant-name contoso

2. Install the add-ons and create indexes:

bash skills/splunk-microsoft-cloud-setup/scripts/setup.sh --install --create-index

3. Configure the Entra app registration (account-setup.md) and enable inputs.

4. Validate:

bash skills/splunk-microsoft-cloud-setup/scripts/validate.sh

5. Score post-ingest readiness:

bash skills/splunk-data-source-readiness-doctor/scripts/setup.sh \
  --phase collect --source-pack microsoft_o365_management_activity

Use --products o365 or --products mscs to act on a single add-on. See reference.md for the full input/account model, source types, CIM mapping, and the Entra/Azure AD path-selection guidance.