Security teams rarely have just one of anything. Most SOCs run separate production, staging, and development accounts. Large enterprises segment by region, business unit, or brand. And managed security service providers (MSSPs) watch over many customers at once. Traditionally, ISVs have used the following configuration – one connector for one product (or workspace), over as many instances of that product as are implemented. We set out to simplify and streamline that experience.
Today we're excited to announce the public preview of multi-account support for codeless connectors in Microsoft Sentinel. A single connector built on the Codeless Connector Framework (CCF) can now support multiple, independently deployable connections in the same workspace, each shown in one unified list so that one connector scales to however many accounts a customer runs.
What's new
The current CCF separates a connector's user interface from its connection configuration. That separation is what makes multiple connections possible. With the multi-account pattern, a connector provides:
- A unified connections list: Every connection appears as its own row, labeled with the details that identify it such as account name, tenant ID, or environment (as seen in the screenshot above).
- An Add connection experience: Users add another connection through a guided form without disturbing the connections that already exist.
- Independent lifecycle per connection: Each connection is deployed, edited, and deleted on its own. Removing one leaves the others untouched.
- Shared, efficient ingestion: All connections flow through the same data collection rule and land in the same table, so adding connections doesn't multiply your ingestion plumbing.
The result is a clean, predictable way to bring many sources of the same product into one Sentinel workspace.
In brief, here’s how it looks in practice: Under the hood, the connector definition that renders the UI is shared, and so are the ingestion resources — the data collection rule, the data collection endpoint, and the destination table. What's created per connection is a single lightweight data connector resource with a unique name, tagged with the metadata that labels it in the grid. That unique name is what lets connections coexist instead of overwriting one another.
Microsoft recommends all new CCF connectors support multi-account where appropriate. For a full walkthrough, annotated JSON, and an authoring checklist, see our MS Learn documentation on the topic.
Use Cases for having your Sentinel Connector utilize the Multi Account capabilities
- Multiple accounts for an ISV
- Different regional accounts
- Developer/QA Accounts
- Pre-Production Cloud Environments
- MSSP
- Multiple customers streaming logs to same Sentinel Instance
The pattern fits the everyday shape of security operations. Whether you are a team consolidating production and non-production accounts for one product, or an MSSP centralizing several customers' sources in a shared workspace, you now have one connector with many connections, and just one place to investigate.
Featured Early Adopter
One company that has already implemented this feature is Semperis, via their Lightning connector.
|
Semperis Lightning integrates with Microsoft Sentinel to deliver deep visibility into identity‑centric risk across Active Directory and Microsoft Entra environments. The connector ingests identity security telemetry such as indicators of exposure, Tier 0 assets, and attack path insights from multiple Semperis accounts into Sentinel, enabling security teams to correlate identity risks with broader security signals. By bringing rich identity context into Sentinel analytics, hunting, and investigations, this integration helps organizations detect, prioritize, and respond to identity‑driven attacks more effectively across hybrid identity infrastructures. |
And here is what Engineering Team Lead at Semperis, David Bagdasarian had to say about the new Multi-Account feature:
Get started
If you are a security professional looking to take advantage of this feature across your own environments, look for connectors that present a connections list and an Add connection action and bring all your sources into one workspace.
If you are an ISV interested in implementing multi-account functionality in your Microsoft Sentinel CCF connector, review the MS Learn documentation as a first step. If additional assistance is needed, the App Assure team is available to provide expert guidance for building and publishing your multi-account connector. Reach out to us via our intake form.
Recent Microsoft Sentinel Public Preview Announcements
- Public Preview Announcement: Empower Real-Time Security with Microsoft Sentinel’s CCF Push Feature | Microsoft Community Hub
- Accelerate connectors development using AI agent in Microsoft Sentinel | Microsoft Community Hub
- Extending Sentinel Data Integration: Azure Blob Storage Support for CCF Connectors | Microsoft Community Hub
- Public Preview: Nested API Support Comes to Microsoft Sentinel CCF | Microsoft Community Hub
Microsoft Sentinel is an industry-leading SIEM & AI-first platform powering agentic defense across the entire security ecosystem.