Microsoft Sentinel to Defender Migration GuideSummary Microsoft is transitioning Microsoft Sentinel from the Azure portal to a unified Microsoft Defender portal experience. To support this change, we have released a new Defender integration "Microsoft Defender Incident ingestion integration for Security Operations" to ServiceNow Store. In addition, we provide a migration utility shipped in defender integration that enables you to migrate your existing Sentinel integration configurations to the Defender integration. The utility ensures a structured and controlled transition, including profile migration, incident mapping, and incident migration. Prerequisites Before you start migrating configurations, ensure that the following requirements are met: Transition your Microsoft Sentinel environment to the Defender portal. (Link)The Microsoft Defender integration is installed.At least one Defender integration configuration is created.Required connectivity to both Sentinel and Defender is verified. Migration will not proceed unless these conditions are met. Accessing the Migration Utility Navigate to the Migration Utility module. In the Application Navigator, select All.In the filter field, type 'Sentinel to Defender Migration'.Under Microsoft Defender Integration, select 'Sentinel to Defender Migration'. Review the list of available Sentinel integration configurations.Map each Sentinel integration configuration to a corresponding Defender integration configuration.Note: If you wish not to migrate any Sentinel profile, select "Migration skipped for this configuration" option from the mapping dropdown.Select Start Migration to begin the process. Pre-Migration Validation When migration starts, the system performs the following validation checks: Sentinel connectivity is verified.Defender connectivity is verified.Recent sample incidents are fetched from Sentinel.Provider information is validated. If any validation fails: The integration configuration is marked Precheck Failed.Profile and incident migration will not start for that configuration. Skip Migration Option If you do not want to migrate a specific integration configuration: Select the Skip Migration option from the dropdown.The configuration will be excluded from migration.You can migrate it later if needed. Profile Migration Process What Happens During Profile Migration All Sentinel profiles associated with the selected integration configuration are identified.Profiles are processed sequentially, one at a time.When a profile is picked for migration: Profile data is transformed into a Defender-compatible format.The corresponding Defender profile is created.Migration references are recorded for tracking. If transformation fails or user input is required: If the process fails, the Defender profile will not be created.The profile is flagged in the Profile Migration related list with an actionable error message for review and correction. Profile Migration Status Definitions StatusWhat it meansSuccessThe Sentinel profile is successfully migrated. Incident mapping starts automatically. After incident migration completes, the Defender profile activation state matches the original Sentinel profile state.User action requiredSome fields could not be migrated automatically due to payload mismatch. Both Sentinel and Defender profiles are deactivated. The user must update the required fields before activating the Defender profile.Note: Incident mapping and migration will still run. After successful incident migration, the Defender profile remains inactive until manually activated. If incident migration fails, the Sentinel profile state is restored to its original state.FailedProfile migration was not completed. Incident mapping and migration will not start. The profile requires review before manual retry. Incident Mapping Process The Incident Mapping process identifies active Sentinel incidents associated with the migrated profile and prepares the corresponding mappings with the Defender incidents. The system validates connectivity, applies retry logic for temporary API issues, and ensures that incidents are properly linked before creation in Defender. After the profile migration process is completed: The sentinel profile is automatically deactivated prior to initiating the incident mapping process.Active Sentinel incidents are retrieved.Mapping entries between Sentinel and Defender incidents are prepared.Profiles from the same source are processed sequentially.Profiles from different sources may run in parallel. In case of issues due to API failures: The system retries automatically using exponential backoff.Up to 3 retry attempts are performed. If all 3 retries fail: Incident mapping is marked Failed.Incidents for that profile are not mapped.The Sentinel profile is reactivated if it was active before migration. If an error occurs after partial retrieval: No incidents are mapped.The entire profile's incident mapping is marked as failed. Manual Retry for Failed Incident Mapping If incident mapping fails after 3 automatic retries: Open the affected profile.Select Retry Migration. During retry: The Azure Sentinel profile is deactivated.Retry count is reset.Existing mapped incidents are not re-fetched.The system performs up to 3 automatic retries again. Incident Mapping Status Definitions StatusWhat it meansPendingThe request is waiting to be processed, or a temporary issue occurred, and a retry has been scheduled.In ProgressThe mapping process is currently running, or mapping has completed, and Defender incident creation has started.FailedThe process could not be completed after all retry attempts were exhausted. Incident Migration Process The Incident Migration process creates Defender incidents based on the mapped Sentinel incidents. It preserves the associated Security Incident Records (SIRs), maintains relationships, and logs any errors for review in the related lists to ensure accurate and complete migration. During incident migration: Active Sentinel incidents associated with the profile are identified.Defender incidents are created and linked appropriately.The associated Security Incident Record (SIR) is preserved.Errors are flagged with clear messages. Note: If multiple Sentinel incidents map to a single Defender incident, multiple related records are created accordingly. Incidents with issues appear in the Incident Migration related list. Bi-Directional Behavior After migration: Incidents created in via Defender portal follow Defender's synchronization behavior.Incidents created in Sentinel and mapped to Defender maintain comment and closure synchronization via the Sentinel Configuration.If field update synchronization is enabled, Defender manages updates.The Security Incident Record integration source field remains unchanged during migration. Post - Migration Review actions After the migration is completed, review for the below details: Profile Migration related listIf a profile requires correction: Update the necessary fields.Activate the Defender profile manually. Incident Migration related list