Update reliability-defender-devops.md

Author: j0tr

articles/reliability/reliability-defender-devops.md

@@ -12,66 +12,70 @@ CustomerIntent: As a cloud architect/engineer, I need general guidance reliabili
 
 # Reliability in Defender for DevOps
 
-This article describes reliability support in [Defender for DevOps](../defender-for-cloud/defender-for-devops-introduction.md), which includes [cross-region recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity). For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
+This article describes reliability support in [Microsoft Defender for Cloud DevOps security features](../defender-for-cloud/defender-for-devops-introduction.md), which includes [cross-region recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity). For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
+
+This article is specific to recover in the case of a region outage.  If you are looking to move your existing DevOps connector to a new region, please see [Common questions about Defender for DevOps](https://learn.microsoft.com/azure/defender-for-cloud/faq-defender-for-devops#can-i-migrate-the-connector-to-a-different-region-)
 
 
 ## Cross-region disaster recovery and business continuity
 
 [!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
 
-Defender for DevOps supports single-region disaster recovery. As such, a multi-region disaster recovery process simply implements [that single-region disaster recovery process outlined in this document](#single-region-disaster-recovery-process). 
+Microsoft Defender for Cloud DevOps security supports single-region disaster recovery. As such, a multi-region disaster recovery process simply implements the [single-region disaster recovery process outlined in this document](#single-region-disaster-recovery-process). 
 
 
 ### Supported regions
 
-Defender for DevOps is only supported in the following regions: 
-
-| Americas | Europe | Asia Pacific |
-| ----- |----|--|
-| Canada Central (Coming soon)| North Europe | Australia East|
-|Central US   |Sweden Central | East Asia (Coming soon)|
-| East US |UK South| Japan East (Coming soon)|
-|West US (Coming soon)|UK West (Coming soon) ||
-|| West Europe||
+For regions that support DevOps security in Defender for Cloud, see [DevOps security region support](https://learn.microsoft.com/azure/defender-for-cloud/devops-support#cloud-and-region-support).  
 
 
 ### Single-region disaster recovery process
 
-The single region disaster recovery process for Defender for DevOps is based on the [Shared Responsibility model](/azure/security/fundamentals/shared-responsibility), and so includes both customer and Microsoft procedures.
+The single region disaster recovery process for DevOps security features is based on the [Shared Responsibility model](/azure/security/fundamentals/shared-responsibility), and so includes both customer and Microsoft procedures.
 
 #### Customer responsibility
 
-When a region goes down, your configurations for the connector of that region is lost. Lost configurations include customer tokens, auto discovery configurations, and ADO annotations configurations. To recover, you'll need to recreate a new connector in a new region.  
+When a region goes down, your configurations for the connector of that region is lost. Lost configurations include customer tokens, auto discovery configurations, and ADO annotations configurations.  
 
->[!TIP]
->You can use an existing connector in the new region, as long as it's authenticated to have access to the Source Code Management (SCM) organizations of the old connector.
+To request recovery of a connector created in a downed region:
 
-To create a new connector in a new region:
+1. Create a new connector in a new region. See onboarding documentation for [Azure DevOps](https://learn.microsoft.com/azure/defender-for-cloud/quickstart-onboard-devops), [GitHub](https://learn.microsoft.com/azure/defender-for-cloud/quickstart-onboard-github), and/or [GitLab](https://learn.microsoft.com/azure/defender-for-cloud/quickstart-onboard-gitlab).
+    >[!NOTE]
+    >You can use an existing connector in the new region, as long as it's authenticated to have access to the scope of DevOps resources in the old connector.
 
-1. Copy the Resource ID of the old connector of the region that has the outage.
+1. Open a new support request to release ownership of the DevOps resources from the old connector.
+    1.  In Azure portal, navigate to Help + Support
+    1.  Fill out the form:
+        1.  Issue type: `Technical`
+        1.  Service type: `Microsoft Defender for Cloud`
+        1.  Summary: "Region outage - DevOps Connector recovery"
+        1.  Problem type: `Onboarding and Settings`
+        1.  Problem subtype: `DevOps security`
 
-1. Open a ticket on Defender for DevOps to release ownership of the Source Code Management (SCM) organizations of the old connector. You can specify specific organizations or all organizations.
+1. Copy the Resource ID of the new and old DevOps connectors. This information is available in Azure Resource Graph.  ResourceID format:
 
-1. Once the old SCM organizations have been released and new entities appear for the new connector, recreate the annotation configuration if needed.
+   ```
+   /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Security/securityConnectors/{connectorName}
 
+1. Once the DevOps resources have been released from the old connector and appear for the new connector, [reconfigure the pull request annotations](https://learn.microsoft.com/azure/defender-for-cloud/enable-pull-request-annotations) as needed.
     >[!NOTE]
-    >The time it takes to recreate the annotation configuration is proportional for how long it takes for the new connector to discover all the SCM organizations.
+    >The time it takes to reconfigure the pull request annotation configuration is proportional for how long it takes for the new connector to discover all the DevOps resources.
 
-1. When the old region recovers from the outage, the new connector is made primary and you can safely delete the old connector.
+1. The new connector will be made primary. When the region recovers from the outage, you can safely delete the old connector.  
 
 
 
 #### Microsoft responsibility
 
-When a region goes down and you have established the new connector, Microsoft recreates all alerts, recommendations, and Security Graph (SG) entities from the old connector into the new connector.
+When a region goes down and you have established the new connector, Microsoft recreates all alerts, recommendations, and Cloud Security Graph entities from the old connector into the new connector.
 
 >[!IMPORTANT]
-> Microsoft doesn't recreate history for some functionalities, such as container mapping data from previous runs, alerts data more than one week old, and IaC mapping history data.
+> Microsoft doesn't recreate history for some functionalities, such as container mapping data from previous runs, alerts data more than one week old, and infrastructure as code (IaC) mapping history data.
 
 
 #### Test your disaster recovery process
 
-To test your disaster recovery process, you can simulate a lost connector by deleting your primary connector.
+To test your disaster recovery process, you can simulate a lost connector by creating a second connector and following the support steps above.
 
 ## Next steps