MicrosoftDocs/azure-devops-docs/docs/migrate

Update migration guide with wiki migration notes Added notes about wiki comments and project section migration limitations.

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-devops-docs (branch main) (#9745) * Merge main > LIVE (#9663) * MDP: Update network validation script * Update docs/managed-devops-pools/configure-networking.md Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> * Update script to handle http Urls * Updated PowerShell script * Update script note * Apply suggestions from code review Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> * Add endpoint to the script * Update * ELM public preview (#9661) * audit updates * elm public preview * default enabled * Update docs/organizations/audit/auditing-streaming.md Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> * Update auditing-streaming.md --------- Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> Co-authored-by: James Barnett <v-jabarnett@microsoft.com> * Update script * Apply batched suggestions from code review Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Add anchor links * Update script --------- Co-authored-by: Steve Danielson <Steve.Danielson@microsoft.com> Co-authored-by: Steve Danielson <steved0x@github.com> Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> Co-authored-by: James Barnett <v-jabarnett@microsoft.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com> * Document `AZP_AGENT_DEFAULT_MAP_DOCKER_SOCKET_TO_FALSE` @ container proc (#14402) * Document `AZP_AGENT_DEFAULT_MAP_DOCKER_SOCKET_TO_FALSE` @ container proc This is useful short-term for mass-deployments when it's impractical and unrealistic to make large changes on suddenly-updated agents. This env var toggle has been added in the same PR https://github.com/microsoft/azure-pipelines-agent/pull/5627, but it looks that the docs writers had forgotten to record this change for better discovery. * Update Docker socket mapping instructions in documentation Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Update Docker socket mapping explanation in documentation Clarified the behavior of the agent host environment variable regarding Docker socket mapping in container jobs. --------- Co-authored-by: chcomley <35748196+chcomley@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-devops-docs (branch main) (#9699) (#14403) * Merge main > LIVE (#9663) * MDP: Update network validation script * Update docs/managed-devops-pools/configure-networking.md * Update script to handle http Urls * Updated PowerShell script * Update script note * Apply suggestions from code review * Add endpoint to the script * Update * ELM public preview (#9661) * audit updates * elm public preview * default enabled * Update docs/organizations/audit/auditing-streaming.md * Update auditing-streaming.md --------- * Update script * Apply batched suggestions from code review * Add anchor links * Update script --------- * Document `AZP_AGENT_DEFAULT_MAP_DOCKER_SOCKET_TO_FALSE` @ container proc (#14402) * Document `AZP_AGENT_DEFAULT_MAP_DOCKER_SOCKET_TO_FALSE` @ container proc This is useful short-term for mass-deployments when it's impractical and unrealistic to make large changes on suddenly-updated agents. This env var toggle has been added in the same PR https://github.com/microsoft/azure-pipelines-agent/pull/5627, but it looks that the docs writers had forgotten to record this change for better discovery. * Update Docker socket mapping instructions in documentation * Update Docker socket mapping explanation in documentation Clarified the behavior of the agent host environment variable regarding Docker socket mapping in container jobs. --------- * Update docs/pipelines/process/container-phases.md --------- Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com> Co-authored-by: chcomley <35748196+chcomley@users.noreply.github.com> Co-authored-by: Steve Danielson <Steve.Danielson@microsoft.com> Co-authored-by: Steve Danielson <steved0x@github.com> Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> Co-authored-by: James Barnett <v-jabarnett@microsoft.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com> Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com> Co-authored-by: Hector <v-ndat@microsoft.com> Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: v-regandowner <97987445+v-regandowner@users.noreply.github.com> * Add clarification for impact of PAT disable option on git operations (#14404) * Add clarification for impact of PAT disable option on git operations Add clarification for impact of PAT disable option on git operations like clone, fetch, pull, push, etc. * fix typo * Update application access policies and dates Updated the date for application access policies and clarified restrictions on personal access token creation. --------- Co-authored-by: chcomley <35748196+chcomley@users.noreply.github.com> * Correct and enhance user licenses worksheet with examples (#14405) * Correct and enhance user licenses worksheet with examples Updated the user licenses worksheet with example values and correction. * Update user licenses worksheet header and content Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com> Co-authored-by: chcomley <35748196+chcomley@users.noreply.github.com> Co-authored-by: Steve Danielson <Steve.Danielson@microsoft.com> Co-authored-by: Steve Danielson <steved0x@github.com> Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> Co-authored-by: James Barnett <v-jabarnett@microsoft.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com> Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com> Co-authored-by: Hector <v-ndat@microsoft.com> Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: v-regandowner <97987445+v-regandowner@users.noreply.github.com> Co-authored-by: nimbusnext-malhar <152470568+nimbusnext-malhar@users.noreply.github.com> Co-authored-by: Björn Sundling <bjorn.sundling@gmail.com>

Apply suggestions from code review Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com>

Apply suggestions from code review Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com>

Apply suggestions from code review Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>

Correct migration guidance that says a region mismatch blocks migration The Data Import Service no longer blocks a migration when the DACPAC storage account or the SQL Azure VM is in a different Azure region from the destination organization. A single server-side validation gated both methods, so removing it unblocked both. Correct only the statements that are no longer accurate: - migration-overview.md: temporary infrastructure no longer has to be deployed in a supported region. - migration-prepare-test-run.md: a SQL Azure VM in a different region no longer fails to start, it warns and asks for confirmation. The storage container is a performance recommendation, not a requirement. Correct the premise of the storage firewall note, which asserted the storage account must be same-region, and drop the same claim from its workaround list. - migration-test-run.md: DACPAC storage placement is a performance recommendation, not a start condition. - migration-troubleshooting.md: VS403271 is no longer expected, so the AzCopy region-move remediation no longer applies. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: be1f9b20-a210-4a3c-a60d-0400b3f6f599

Apply suggestion from @learn-build-service-prod-10[bot] Co-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>

Apply suggestion from @learn-build-service-prod-10[bot] Co-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>

Align DACPAC firewall guidance with Microsoft Learn style guidance Apply the Microsoft Learn contributor guidance at https://learn.microsoft.com/en-us/contribute/content/: - Alerts: the guidance says to avoid note and important boxes because readers skim past them, to put the information directly in the article text, and to never place multiple alerts next to each other. The page already had six alerts, and this change had added three more. Convert the section intro note and the Option 1 note to body text, and keep a single Important box for the same-region limitation, which is essential information required for user success. - Move the Option 2 workaround list out of the alert and into a regular bulleted list so the alert stays short. - Text formatting guidelines: bold is reserved for UI elements. Remove the bold lead-ins "Applies to the SQL Azure VM migration method" and "Same-region limitation for DACPAC migrations". Bold is retained only for the Public network access, All networks, and Selected networks UI labels. - Use active voice and second person, "you can't use this option to allow access" rather than "this option can't be used". - Remove nested parentheses in the Option 1 paragraph. Verified with markdownlint against the repository .markdownlint.json. No content changes to the guidance itself. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: d89eaf19-9c69-4933-a77e-5defb6f20b7d

Apply final review feedback to DACPAC storage firewall guidance Reconcile the "Restrict access to Azure DevOps Services IPs only" section with the final consolidated review feedback: - Add a section intro note describing which parties access the DACPAC storage container: the upload machine and the hosted Data Import Service. Clarify that Migrator validate and prepare connect to the collection database and Microsoft Entra ID, and that import submits the package over HTTPS with a PAT and reads no storage container. - Remove the "create the storage account in a different Azure region" workaround. The import service requires the DACPAC to be in the same region as the destination organization and rejects a mismatch with VS403271, so it is not a valid workaround. - Reorder the remaining Option 2 workarounds so the more secure SQL Azure VM and NSG service tag path comes first. - Add the revert instruction to the "All networks" fallback, and note that leaving the storage account open is a security regression. - State the same-region limitation as a requirement rather than a conditional, since the storage account must be in the destination region. Ref: ICM 51000001117137. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: d89eaf19-9c69-4933-a77e-5defb6f20b7d

Clarify DACPAC storage firewall guidance in prepare test run migration Add applicability note to Option 1 (Service Tags) and a same-region limitation Important box to Option 2 (IP List) for DACPAC migrations. Ref: ICM 51000001117137. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 373d3ce2-5b42-4f70-a5ef-8a8536178a03

GitHub customer feedback - discrepancy + refresh (#9308)

ELM quick updates: number/sequenced article tasks + ELMs (plural) + move docset to Repos TOC (#9288) * number/sequenced article tasks + ELMs (plural) * relocate docset and do redirects * relocate * LFS (future)

NEW: Documentation for Enterprise Live Migration (ELM) (#9283) * Add documentation for Enterprise Live Migrations (ELM) - Create overview.md to introduce ELM and its core capabilities. - Add prerequisites.md detailing requirements for ELM setup. - Implement start-migration.md to guide users through authentication and initial synchronization. - Establish toc.yml for navigation within ELM documentation. - Develop troubleshoot.md to assist users in diagnosing and resolving common ELM errors. * Update docs/migrate/elm/prerequisites.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update docs/migrate/elm/prerequisites.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update docs/migrate/elm/prerequisites.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update docs/migrate/elm/prerequisites.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * remove troubleshooting doc, small updates, rename folder from elm * edits * cutover one word, file rename * updates * remove child TOC * elm singular --------- Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com>

Merge branch 'main' into panos/fusion/data_import

bookmark fixes

BULK UPDATES: Replace "Related articles" with "Related content" and other stylistics (#9220) * Update documentation to replace "Related articles" with "Related content" across multiple reports and guides; improve clarity and consistency in language throughout various sections; enhance instructions and descriptions for better user understanding. * build warning fix for bookmark * Remove deprecated ms.assetid metadata from all articles * build warning fixes, invalid mapping * Revert "Remove deprecated ms.assetid metadata from all articles" This reverts commit 6252100cef55baf68bd9dd27a0ddb473ed16a217.

Typo fix - Step 4 in migration test run doc typo

Move SQL Azure VM steps off DACPAC page; clarify SAS token container scope - Remove duplicate 'Configure your collection for migration' and 'Configure the migration specification file to target the VM' subsections from Step 2 of migration-test-run.md. These steps belong only to the SQL Azure VM alternative documented on migration-prepare-test-run.md and appearing on the DACPAC page caused confusion. - Replace the removed content with a pointer note linking to the SQL Azure VM alternative for users where the Data Migration Tool blocks the DACPAC method. - In Step 4 (Generate an SAS token), add an Important note that the SAS token must be generated at the container level, not at the storage account or individual blob level. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

refreshes