SEI-14315 Update SEI Azure DevOps Integration Documentation (#11659)

* SEI-14315

* SME Review

Author: alai97

docs/software-engineering-insights/shared/integrations/azure-devops.mdx

@@ -16,7 +16,7 @@ Azure DevOps Services is a cloud offering. To integrate with the on-premises off
 
 ### Requirements
 
-The following permissions and settings are required to use the **SEI AzureDevOps Services integration**:
+The following permissions and settings are required to use the **SEI Azure DevOps Services integration**:
 
 <Tabs>
 <TabItem value = "OAuth" label = "OAuth" default>
@@ -32,22 +32,26 @@ The following permissions and settings are required to use the **SEI AzureDevOps
 </TabItem>
 <TabItem value = "PAT" label = "Personal Access Token">
 
-Before you configure the **SEI AzureDevOps integration**, you must generate a **Personal Access Token**.
+Before you configure the **SEI Azure DevOps integration**, you must generate a **Personal Access Token**. 
 
-1. Sign in to your **Azure DevOps organization** with **Microsoft account** using the following url: `https://dev.azure.com/{yourorganisation}`.
+The SEI Azure DevOps integration only ingests projects accessible to the provided token. If access changes later, ingestion for those projects will stop until access is restored.
+
+1. Sign in to your **Azure DevOps organization** with your **Microsoft account** using the following URL: `https://dev.azure.com/{yourorganisation}`.
 2. Navigate to your **User Settings**:
-   1. Click on your profile picture in the top right corner.
-   2. Select **Security** from the dropdown menu.
-   3. Under **Personal Access Tokens**, click on the **+ New Token** button.
+   
+   - Click on your profile picture in the top right corner.
+   - Select **Security** from the dropdown menu.
+   - Under **Personal Access Tokens**, click on the **+ New Token** button.
+
 3. In the **Organization** dropdown, select **All accessible organizations**.
 
-:::info
-Due to a limitation in Azure DevOps, the PAT token must be configured with the All accessible organizations scope to ensure Harness can retrieve the user data
-:::
+   :::info
+   Due to a limitation in Azure DevOps, the PAT token must be configured with the All accessible organizations scope to ensure Harness can retrieve the user data.
+   :::
 
 4. Configure the **Scopes** by choosing the required level of access for the token as given below.
 
-<img src={adoPatPermissions} alt="Permissions for an Azure DevOps for the PAT token" width="1000" />
+   <img src={adoPatPermissions} alt="Permissions for an Azure DevOps for the PAT token" width="1000" />
 
 </TabItem>
 </Tabs>
@@ -94,30 +98,32 @@ To ensure your integration can work correctly, refer to the list of [Harness Pla
    * The **Description** and **Tags** are optional.
    * Add the **Personal Access Token** you previously generated in Azure DevOps.
 
-   <img src={adoPat} alt="Add the Azure DevOps PAT" width="1000" />
+      <img src={adoPat} alt="Add the Azure DevOps PAT" width="1000" />
 
    * Select the specific Azure DevOps services you want to integrate:
      * Azure Boards
      * Azure Pipelines
      * Azure Repos
 
-   <img src={adoServices} alt="Add Azure DevOps Services Services" width="1000" />
+      <img src={adoServices} alt="Add Azure DevOps Services Services" width="1000" />
 
    * Click on **Validate Connection** to validate the connection, and once successful, you'll have the integration set up under the **Your Integrations** tab.
 
-:::info
-Different integrations will be automatically created for all the Azure DevOps services. 
+      :::info
+      Different integrations will be automatically created for all the Azure DevOps services. 
 
-For example:
+      For example:
 
-* Azure integration - Boards for Azure Boards
-* Azure integration - Pipelines for Azure DevOps Pipelines
-* Azure integration - Repos for Azure DevOps Repos
-:::
+      * Azure integration - Boards for Azure Boards
+      * Azure integration - Pipelines for Azure DevOps Pipelines
+      * Azure integration - Repos for Azure DevOps Repos
+      :::
 
 </TabItem>
 </Tabs>
 
+After adding the integration, it may take up to 24 hours for data to fully sync to SEI. During this time, any widgets you set up in Insights may not display data until the sync is complete.
+
 ### Limitations
 
 1. The Azure DevOps integration currently ingests and retains data for the last 90 days.
@@ -129,10 +135,11 @@ For example:
    * CICD Pipeline Jobs Duration Report
    * CICD Pipeline Jobs Duration Trend Report
 4. The integration does not accurately reflect the pipeline stage status across the widgets.
-
-:::note
-After adding the integration, it may take up to 24 hours for data to fully sync to SEI. During this time, any widgets you set up in Insights may not display data until the sync is complete.
-:::
+5. If the access token used for the integration loses access to some projects (i.e. when projects are removed or permissions change), SEI will stop ingesting data from those projects. Data ingestion continues for the remaining accessible projects.
+   
+   If project access is restored later, ingestion resumes **incrementally** for the newly accessible projects. Historical data will not be backfilled automatically, since SEI has no reference point for when to start ingestion.  
+   
+   To capture historical data for newly added projects, contact [Harness Support](/docs/software-engineering-insights/sei-support) to schedule a manual ingestion re-run for the selected projects.
 
 ### See also