Domain separation and Microsoft Azure Sentinel integration

  • Release version: Zurich
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Domain separation and Microsoft Azure Sentinel integration

    This application supports domain separation, enabling ServiceNow customers to segregate data, processes, and administrative tasks into distinct logical domains. This separation controls user access and visibility across domains, which is essential for multi-tenant environments such as service providers managing multiple customers.

    Show full answer Show less

    Microsoft has extended the deprecation of the Azure Sentinel experience in the Azure portal from March 2026 to March 2027. Customers currently using Azure Sentinel integration with Security Incident Response (SIR) are strongly advised to migrate to the new Defender portal integration. This new integration includes a migration utility that preserves existing incident continuity.

    Key Features

    • Domain separation operates at run time, isolating UI elements, cache keys, reporting, rollups, and aggregations per domain.
    • Support for multiple tenants requires the instance owner to configure the application accordingly.
    • Integration with Azure Sentinel supports domain-specific configuration and scheduled jobs to maintain data segregation.
    • Scheduled jobs related to Azure Sentinel (e.g., fetching alerts, syncing comments, status updates) must be replicated and run separately per domain, using a domain-specific user assigned the snsi.admin role.
    • The domain-specific user must be created within the target domain using the domain picker; users should not be created in the parent domain and reassigned later.

    Practical Application

    For service providers, domain separation ensures that customer data and interactions remain isolated and secure. For example, when a service provider responds to a tenant-customer’s chat message, the customer sees only the relevant responses within their domain.

    To implement domain separation with Azure Sentinel integration:

    • Create a user with the snsi.admin role in each domain using the domain picker.
    • Disable existing Azure Sentinel scheduled jobs globally.
    • Replicate the necessary Azure Sentinel scheduled jobs for each domain.
    • Configure each job to run as the domain-specific snsi.admin user.
    • Run the jobs to ensure data flows correctly and remains segregated per domain.

    Key Outcomes

    • Proper enforcement of data and access separation across multiple domains and tenants.
    • Maintained integrity and continuity of Azure Sentinel alerts and incidents within each domain.
    • Improved security and compliance by ensuring users only access data relevant to their domain.
    • Preparedness for the upcoming transition from Azure Sentinel to Defender portal integration, simplifying future migrations.

    Domain separation is supported for this application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Important:

    Microsoft has extended the deprecation of the Azure Sentinel experience in the Azure portal from March 2026 to March 2027.

    If you are currently using the Azure Sentinel integration with Security Incident Response (SIR), we strongly recommend migrating to the new Defender portal integration as soon as possible. The Defender integration includes a built-in migration utility that automatically converts your existing Sentinel profiles into Defender profiles, while ensuring continuity of incidents created through Sentinel after the transition. For more information, see Microsoft Sentinel to Defender Migration Guide.

    Support level: Basic

    • Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
    • The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
    • The owner of the instance must set up the application to function across multiple tenants.

    Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.

    For more information on support levels, see Application support for domain separation.

    How domain separation works in the Microsoft Azure Sentinel integration

    Follow these steps to achieve domain separation:
    • Create a user with the sn_si.admin role in the respective domain.
      Note:
      When you create the profile, use the domain picker to select a domain. Do not create the user in the parent domain and later change the domain of the profile. You should have a user for each domain for your profile with the sn_si.admin role. Use this user to create or modify settings in the profile.
    • Disable existing scheduled jobs.
    • Replicate the following scheduled jobs for every domain:
      • Azure Sentinel Fetching Alerts & Entities
      • Azure Sentinel Comments Sync
      • Azure Sentinel Status Update
      • Azure Sentinel Profile Process
      • Azure Sentinel Process Raw Data
      • Azure Sentinel Data Cleanup
      • Azure Sentinel Historic Comment Pull
    • Change the Run as from the system user to the user with the sn_si.admin role in the respective domain and then run the scheduled job.

    The following example shows how to replicate the Azure Sentinel comments and Status update job and run the job as a system user.

    Replicate Azure Sentinel comments and Status update job and run as system user.