Unable to deploy code to another subscription

Xhevahir Mehalla 160 Reputation points
2024-06-10T16:43:57.5733333+00:00

Hello

I need help with smth and this is the current setup:

  1. Have many synapse Pipelines on subscription A
  2. I have created another subscription and workspace on another client tenant/subscription B.
  3. I created linked service and Integration Runtime on Subscription B (which is self -hosted ) on Oracle OCI but has different name than Subs A
  4. I publish from Workspace from A and want to Deploy to B - but again the linked services and integration runtimes have different names
  5. I use devops and use Synapse workspace deployment
  6. I copied the template/params json files into develop branch
  7. When I run the yaml pipelines I get an error : An error occurred during execution : cannot find the IR and Linkedservice
  8. IR self-hosted LocalPentahoFileStorage is on source but not target
  9. ConnectToOracle LinkService is on source but in target has different name and based on different self -Hosted IR
  10. What actions do I need to take using the new names on the old code:

a) do I need to change the template.json to update the IR and Linked service with new names

or smth else.

Is taking too much of time to figure out this.

Thanks

Xhev

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,622 questions
Accepted answer
  1. BhargavaGunnam-MSFT 28,616 Reputation points Microsoft Employee
    2024-06-10T19:02:49.1233333+00:00

    Hello Xhevahir Mehalla,

    Can you confirm the exact names of the Integration Runtime and Linked Services in both Subscription A and Subscription B?

    Are there any differences in the configuration details of the IR and Linked Services between the two subscriptions, apart from the names?

    Here are some suggestions for the issue you are facing:
    Use parameters within your ARM template to dynamically set the names of the linked services and integration runtimes during deployment. This allows you to use the same template across different environments without manual changes.You can also consider using variable groups to manage environment-specific configurations. You can define variables for each environment and link them to your pipeline.

    Before deploying, validate the connections of your linked services in the Azure Synapse Studio to ensure they are correctly configured and can connect to the respective data stores or services.

    and make sure the Synapse workspace deployment task in your DevOps pipeline is configured to reference the correct subscription and workspace in Subscription B.

    You can reference this demo

    I hope this helps.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest