Hi @scott cooke
Welcome to Microsoft Q&A platform and thanks for posting your question here.
It seems that you are facing an issue with the deployment of external data sources in Azure Synapse. The problem is that the external data sources deployed point to the lower (dev) environment, causing warnings in the Prod environment.
One way to address this issue is by parametrizing the path or location of the external table. Another approach is to ignore the deployment of external data sources to prevent overwriting the production values.
Parametrize the Path: If you want to change the external data source path during deployment in Synapse Workspace v2, you can verify if the deployment task allows parameterization. This requires defining parameters for the path or location of the external table and utilizing them in the deployment process.
Ignore Deployment: Another approach is to modify the deployment process to ignore the deployment of external data sources. This would require adjusting the deployment task configuration to exclude the external data sources from the deployment process.
To fix the issue with the Linked Service not being found, you need to update the external data sources to point to the correct Linked Service in the Prod environment. You can do this by updating the external data sources using the ALTER EXTERNAL DATA SOURCE statement in SQL.
I hope this information helps you. Let me know if you have any further questions or concerns.