Skip to content

Commit 0c49f8d

Browse files
committed
Update how-to-move-workspace-from-one-region-to-another.md
1 parent 3e50297 commit 0c49f8d

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/synapse-analytics/how-to-move-workspace-from-one-region-to-another.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -365,9 +365,7 @@ This screenshot from the Azure DevOps repo shows the workspace template files fo
365365

366366
:::image type="content" source="media/how-to-move-workspace-from-one-region-to-another/devops-repo-workspace-publish.png" alt-text="Screenshot that shows workspace-publish.":::
367367

368-
You can use the workspace template to deploy artifacts and pipelines to a workspace by using the Azure DevOps release pipeline as shown in the following screenshot.
369-
370-
:::image type="content" source="media/how-to-move-workspace-from-one-region-to-another/release-pipeline.png" alt-text="Screenshot that shows synapse-release-pipeline.":::
368+
You can use the workspace template to deploy artifacts and pipelines to a workspace by using the Azure DevOps release pipeline.
371369

372370
If the workspace isn't integrated with GitHub or Azure DevOps, you'll have to manually re-create or write custom PowerShell or Azure CLI scripts to deploy all the artifacts, pipelines, linked services, credentials, triggers, and Spark definitions on the target region workspace.
373371

0 commit comments

Comments
 (0)