Merge branch 'main' of https://github.com/MicrosoftDocs/azure-devops-docs-pr into users/sdanie/508647

Author: Steve Danielson

docs/boards/queries/import-work-items-from-csv.md

@@ -9,7 +9,7 @@ ms.author: chcomley
 author: chcomley
 ms.topic: how-to
 monikerRange: "<=azure-devops"
-ms.date: 11/26/2024
+ms.date: 11/14/2025
 #customer intent: As a team member, I want to import and export work items in CSV format to create or update them in bulk by using Excel.
 ---
 
@@ -43,15 +43,29 @@ To import work items in bulk, your CSV file must include the **Work Item Type**
   - Verify that all fields in the CSV file match the fields for the work item types in the target project.
 - **Handle invalid values:** If the imported CSV file contains work items with invalid values, you must edit and correct these work items after import before they can be saved.
 
+> [!TIP]
+> Work item fields vary between different process templates (Agile, Scrum, CMMI) and Azure DevOps versions. Before importing, verify the available fields for your work item types by:
+> 1. Creating a sample work item of the desired type in your project
+> 2. Viewing the available fields in the work item form
+> 3. Or exporting existing work items to see the current field structure
+> 
+> Field names and availability might differ from the examples shown in this article based on your process template and Azure DevOps version.
+
 Do the following steps to import new work items.
 
 > [!NOTE]  
 > You can import up to 1,000 work items at a time. If you have more than 1,000 work items to import, break them into multiple files and import them separately.
 
 1. Create a local *import.csv* file and open it in Visual Studio Code or Excel.
-2. The file must contain the **Work Item Type** and the **Title** fields. You can include other fields as needed. For a list of default fields, see [Work item field index](../work-items/guidance/work-item-field.md).  
+2. The file must contain the **Work Item Type** and the **Title** fields. You can include other fields as needed. 
+
+   > [!TIP]
+   > To determine the correct field names for your Azure DevOps instance:
+   > - Export a few existing work items from your project to view the exact field names
+   > - Create a new work item and review the available fields
+   > - Check the [Work item field index](../work-items/guidance/work-item-field.md) for standard field references
 
-   The following example includes the **Priority** field.
+   The following example includes the **Priority** field. Your available fields might differ based on your process template:
 
    ```csv
    Work Item Type,Title,Priority
@@ -85,6 +99,13 @@ Do the following steps to import new work items.
 
 ### Tips
 
+- **Field compatibility:** Different Azure DevOps versions and process templates (Agile, Scrum, CMMI, or custom) have different available fields. Always verify field names by exporting existing work items from your project before importing new ones.
+- **Process template differences:** 
+  - **Agile process**: Uses User Story, Task, Bug, Epic, Feature, Test Case
+  - **Scrum process**: Uses Product Backlog Item, Task, Bug, Epic, Feature, Test Case  
+  - **CMMI process**: Uses Requirement, Task, Bug, Epic, Feature, Test Case
+  - Your field names and available options might vary based on which process your project uses.
+
 - **Parent-child links:** You can add parent-child links between work items you import by indenting the title columns, as shown in [Can I import a CSV file that have parent-child links?](#tree-items). However, you can't specify any other link types when you import or update work items.
 - **Default State field:** When you import new work items, the **State** field is set to *New* by default. You can't specify a different state during the import process. If you need to change the state of imported work items, use the following workaround:
 
@@ -120,7 +141,7 @@ Do the following steps to import new work items.
 1. Make the edits to your work items. Your CSV file must contain the **ID**, **Work Item Type**, and **Title** fields. Any other fields you want to include are optional.
 
    > [!NOTE]
-   > When you import identity fields, enter the name and email in the following format `"Display Name <email>"`. For example, to assign work to Jamal Hartnett, specify `"Jamal Hartnett <[email protected]>"`. If you specify a value that isn't recognized as a valid user to the system, you may encounter problems with the import.
+   > When you import identity fields, enter the name and email in the following format `"Display Name <email>"`. For example, to assign work to Jamal Hartnett, specify `"Jamal Hartnett <[email protected]>"`. If you specify a value that isn't recognized as a valid user to the system, you might encounter problems with the import.
 
    In the following example, we change values on existing working items.
 

docs/extend/develop/using-host-dialog.md

@@ -8,7 +8,7 @@ ai-usage: ai-assisted
 monikerRange: '<= azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 07/02/2025
+ms.date: 11/14/2025
 # customer-intent: As an Azure DevOps extension developer, I want to create modal dialogs that block user interaction with the entire page so I can collect user input, display forms, and provide focused user experiences in my extensions.
 ---
 
@@ -29,8 +29,6 @@ Use modal dialogs in your extensions to:
 
 ## Prerequisites 
 
-Before you can create modal dialogs in your Azure DevOps extension, ensure you have the following:
-
 | Category | Requirement | Details |
 |----------|-------------|---------|
 | **Extension setup** | Working extension project | A valid `vss-extension.json` manifest file |
@@ -42,7 +40,7 @@ Before you can create modal dialogs in your Azure DevOps extension, ensure you h
 | **Required packages** | Extension SDK | Install: `npm install azure-devops-extension-sdk` |
 | | Extension API | Install: `npm install azure-devops-extension-api` |
 | **Extension permissions** | Manifest scopes | Include appropriate scopes in `vss-extension.json`, for example: `"vso.work"`, `"vso.project"` |
-| **SDK imports** | Required modules | Import SDK and services: `import * as SDK from "azure-devops-extension-sdk"` and `import { CommonServiceIds, IHostDialogService } from "azure-devops-extension-api"` |
+| **SDK imports** | Required modules | Import SDK and services: `import * as SDK from "azure-devops-extension-sdk"` |
 
 ## Dialog contents
 
@@ -140,78 +138,76 @@ The `uri` property references a page that is rendered within the content area of
 
 ## Show the dialog
 
-To show the dialog (for example, when a user selects an action on a toolbar or menu), call the `openDialog` function on an instance of the HostDialogService, passing the fully qualified identifier of the dialog content, for example `my-publisher.my-extension.registration-form` and any dialog options:
+To show the dialog (for example, when a user selects an action on a toolbar or menu), call the `openDialog` function on an instance of the HostDialogService:
 
 ```javascript
-    import * as SDK from "azure-devops-extension-sdk";
-    
-    SDK.getService<IHostDialogService>(CommonServiceIds.HostDialogService).then((dialogService) => {
-        const extensionCtx = SDK.getExtensionContext();
-        // Build absolute contribution ID for dialogContent
-        const contributionId = `${extensionCtx.publisherId}.${extensionCtx.extensionId}.registration-form`;
-
-        // Show dialog
-        const dialogOptions = {
-            title: "My Dialog",
-            width: 800,
-            height: 600
-        };
-
-        dialogService.openDialog(contributionId, dialogOptions);
-    });
+import * as SDK from "azure-devops-extension-sdk";
+
+SDK.getService(SDK.CommonServiceIds.HostDialogService).then((dialogService) => {
+    const extensionCtx = SDK.getExtensionContext();
+    // Build absolute contribution ID for dialogContent
+    const contributionId = `${extensionCtx.publisherId}.${extensionCtx.extensionId}.registration-form`;
+
+    // Show dialog
+    const dialogOptions = {
+        title: "My Dialog",
+        width: 800,
+        height: 600
+    };
+
+    dialogService.openDialog(contributionId, dialogOptions);
+});
 ```
 
 ## Advanced dialog features
 
-A function can be called when the OK button is selected. This function is specified by `getDialogResult` in the options you provide when showing the dialog.
+A function can be called when the OK button is selected. You specify this function by setting `getDialogResult` in the options you provide when showing the dialog.
 
 If a call to `getDialogResult` returns a non-null value, this value is then passed to the function specified by `okCallback` (also in the options) and the dialog is closed.
 
 In this example, the `attachFormChanged` callback gets called when inputs on the form change. Based on whether the form is valid or not, the OK button is enabled or disabled.
 
 ```javascript
-    import * as SDK from "azure-devops-extension-sdk";
-    import { CommonServiceIds, IHostDialogService } from "azure-devops-extension-api";
-    
-    SDK.getService<IHostDialogService>(CommonServiceIds.HostDialogService).then((dialogService) => {
-        let registrationForm: any;
-        const extensionCtx = SDK.getExtensionContext();
-        const contributionId = `${extensionCtx.publisherId}.${extensionCtx.extensionId}.registration-form`;
-
-        const dialogOptions = {
-            title: "Registration Form",
-            width: 800,
-            height: 600,
-            getDialogResult: () => {
-                // Get the result from registrationForm object
-                return registrationForm ? registrationForm.getFormData() : null;
-            },
-            okCallback: (result: any) => {
-                // Log the result to the console
-                console.log(JSON.stringify(result));
-            }
-        };
-
-        dialogService.openDialog(contributionId, dialogOptions).then((dialog) => {
-            // Get registrationForm instance which is registered in registrationFormContent.html
-            dialog.getContributionInstance("registration-form").then((registrationFormInstance) => {
+import * as SDK from "azure-devops-extension-sdk";
+
+SDK.getService(SDK.CommonServiceIds.HostDialogService).then((dialogService) => {
+    let registrationForm;
+    const extensionCtx = SDK.getExtensionContext();
+    const contributionId = `${extensionCtx.publisherId}.${extensionCtx.extensionId}.registration-form`;
+
+    const dialogOptions = {
+        title: "Registration Form",
+        width: 800,
+        height: 600,
+        getDialogResult: () => {
+            // Get the result from registrationForm object
+            return registrationForm ? registrationForm.getFormData() : null;
+        },
+        okCallback: (result) => {
+            // Log the result to the console
+            console.log(JSON.stringify(result));
+        }
+    };
+
+    dialogService.openDialog(contributionId, dialogOptions).then((dialog) => {
+        // Get registrationForm instance which is registered in registrationFormContent.html
+        dialog.getContributionInstance("registration-form").then((registrationFormInstance) => {
+        
+            // Keep a reference of registration form instance (to be used previously in dialog options)
+            registrationForm = registrationFormInstance;
 
-                // Keep a reference of registration form instance (to be used previously in dialog options)
-                registrationForm = registrationFormInstance;
-                
-                // Subscribe to form input changes and update the Ok enabled state
-                registrationForm.attachFormChanged((isValid: boolean) => {
-                    dialog.updateOkButton(isValid);
-                });
-                
-                // Set the initial ok enabled state
-                registrationForm.isFormValid().then((isValid: boolean) => {
-                    dialog.updateOkButton(isValid);
-                });
-            });                            
-        });
+            // Subscribe to form input changes and update the Ok enabled state
+            registrationForm.attachFormChanged((isValid) => {
+                dialog.updateOkButton(isValid);
+            });
+            
+            // Set the initial ok enabled state
+            registrationForm.isFormValid().then((isValid) => {
+                dialog.updateOkButton(isValid);
+            });
+        });                            
     });
-
+});
 ```
 
 ## Control the OK button
@@ -227,7 +223,7 @@ Initially, the OK button is disabled. However, you can enable/disable this butto
 
 ## Pass values to the dialog
 
-It's possible to pass initial values to dialog content when it is opened in the host dialog.
+It's possible to pass initial values to dialog content when you open it in the host dialog.
 
 ```json
     {
@@ -241,7 +237,7 @@ It's possible to pass initial values to dialog content when it is opened in the
     }
 ```
 
-When the dialog is opened, following options need to be specified to pass `myId`:
+When the dialog opens, the following options must be specified to pass `myId`:
 
 ```javascript
     const dialogOptions = {

docs/migrate/migration-test-run.md

@@ -9,7 +9,7 @@ ai-usage: ai-assisted
 ms.author: chcomley
 author: chcomley
 monikerRange: '<= azure-devops'
-ms.date: 04/04/2025
+ms.date: 11/17/2025
 ms.custom: sfi-image-nochange
 ---
 
@@ -185,7 +185,7 @@ Azure DevOps Services is available in several [Azure geographical locations](htt
 | United Kingdom | United Kingdom South | UKS| 
 | Australia | Australia East | EAU |
 | South America | Brazil South | SBR |
-| Asia Pacific | South India | MA |
+| Asia Pacific | Central India | MA |
 | Asia Pacific | Southeast Asia (Singapore) | SEA |
 | Canada | Central Canada | CC |
 
@@ -258,7 +258,7 @@ If Microsoft Entra Connect isn't configured, all users in the identity map log f
 
 Running a migration with all historical identities has consequences that need to be considered carefully. Only teams with a few users and for which the cost of setting up Microsoft Entra Connect is deemed too high should consider. 
 
-To migration all identities as historical, follow the steps outlined in later sections. When you queue a migration, the identity used to queue the migration is bootstrapped into the organization as the organization owner. All other users are imported as historical. Organization owners can then [add the users back in](../organizations/accounts/add-organization-users.md?toc=/azure/devops/organizations/accounts/toc.json&bc=/azure/devops/organizations/accounts/breadcrumb/toc.json) by using their Microsoft Entra identity. The added users are treated as new users. They don't* own any of their history, and there's no way to reparent this history to the Microsoft Entra identity. However, users can still look up their premigration history by searching for their `\<domain>\<Active Directory username>`.
+To migration all identities as historical, follow the steps outlined in later sections. When you queue a migration, the identity used to queue the migration is bootstrapped into the organization as the organization owner. All other users are imported as historical. Organization owners can then [add the users back in](../organizations/accounts/add-organization-users.md?toc=/azure/devops/organizations/accounts/toc.json&bc=/azure/devops/organizations/accounts/breadcrumb/toc.json) by using their Microsoft Entra identity. The added users are treated as new users. They don't own any of their history, and there's no way to reparent this history to the Microsoft Entra identity. However, users can still look up their premigration history by searching for their `\<domain>\<Active Directory username>`.
 
 The Data Migration Tool displays a warning if it detects the complete historical identities scenario. If you decide to go down this migration path, you need to consent in the tool to the limitations. 
 
@@ -439,7 +439,7 @@ Azure DevOps Services is available in multiple [geographical locations](https://
 | United Kingdom | United Kingdom South | 
 | Australia East | Australia East |
 | Brazil South | Brazil South |
-| India South | India South |
+| India Central | India Central |
 | Canada Central | Canada Central |
 | Asia Pacific (Singapore) | Asia Pacific (Singapore) |
 
@@ -513,7 +513,7 @@ Your team is now ready to begin the process of running a migration. We recommend
 
 > [!NOTE]
 > - If you need to repeat a completed production-run migration for a collection, such as due to a rollback, contact Azure DevOps Services [Customer Support](https://azure.microsoft.com/support/devops/) before you queue another migration.
-- Azure administrators can prevent users from creating new Azure DevOps organizations. If the Microsoft Entra tenant policy is turned on, your migration fails to finish. Before you begin, verify that the policy isn't set or that there's an exception for the user that is performing the migration. For more information, see [Restrict organization creation via Microsoft Entra tenant policy](../organizations/accounts/azure-ad-tenant-policy-restrict-org-creation.md).
+- Azure administrators can prevent users from creating new Azure DevOps organizations. If the Microsoft Entra tenant policy is turned on, your migration fails to finish. Before you begin, verify that the policy isn't set or that there's an exception for the user that's performing the migration. For more information, see [Restrict organization creation via Microsoft Entra tenant policy](../organizations/accounts/azure-ad-tenant-policy-restrict-org-creation.md).
 - Azure DevOps Services doesn't support per-pipeline retention policies, and they aren't carried over to the hosted version.
 
 ### Considerations for rollback plans