ServiceNow developers needed representative Microsoft Sentinel incidents to test SecOps integrations. Each manual request depended on an available SOC analyst and recreated the same test data. I turned that task into a self-service workflow the developers could run from Teams.
I built the workflow with Copilot Studio and Power Automate. It enables a near-real-time Sentinel analytic rule, creates an incident with programmed entities, ATT&CK context and labels, then disables the rule after the testing window.
Making the workflow repeatable required more than an incident-creation trigger. I rejected overlapping runs, added messages showing whether the rule was active or ready, and corrected alert grouping so another run produced a fresh incident instead of appending to an earlier test.
I documented the workflow and handed it to the ServiceNow team. They use it around seven times daily to test different configurations of entities and incident metadata in the integration payload, giving developers known test inputs without repeated requests for an analyst to create incidents.
Methods, evidence & technical decisions
Program the entities and fields under test
The fixture combines identities, devices, ATT&CK tactics and techniques, and labels in a controlled Sentinel incident. I programmed these values for ServiceNow SecOps development so the team could compare the source incident with the context arriving in ServiceNow.
Open this detail ↗Keep each run comparable
Known identities, devices and incident metadata let developers check that integration changes preserve the intended context in ServiceNow. The repeatable inputs make mapping problems easier to isolate without asking analysts to recreate incidents manually.
Open this detail ↗Prevent overlap and reset the analytic rule
The Teams-triggered Copilot Studio and Power Automate flow enables the NRT analytic rule, rejects another run while it is active, reports its state and disables it after the test window. Completion messaging tells the team when the environment is ready for another run.
Open this detail ↗Create a fresh incident, then hand over the workflow
I corrected the rule’s grouping behaviour so a new test generated its own incident and debugged the reset messaging. I then documented invocation and handed the workflow to the ServiceNow team for independent use during integration development.
Open this detail ↗Skills used in this work