microsoft / synapse-support

Repository for public-facing support-driven content for Azure Synapse Analytics

Azure Synapse Analytics Support

This project intends to host notebooks and scripts which supplement public documentation, troubleshooters, and how-to documents for user consumption.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

synapse-support's Issues

Naming a Synapse Pipeline activity "Pipeline" causes pipeline to fail

NB! This is a duplicate of this issue. I wasn't sure where this issue would fit best, so I will leave it up to you to decide

What is the issue
Running a pipeline where an action is named Pipeline causes the run to fail immediately.

Steps to reproduce issue

1. Create a pipeline
2. Add a Synapse Notebook activity and name it "Pipeline"
3. Link it to the notebook and spark pool of your choice

Expected behavior
I would expect one of the following outcomes, in the given order:

1. It should not fail
2. It should report back a more helpful error message
3. It should be documented somewhere if "Pipeline" is a reserved activity name

Observed behavior
The pipeline run fails immediately with the following error message:

{
    "code": "BadRequest",
    "message": null,
    "target": "pipeline//runid/8fd22880-bbfe-41a9-b91d-8ce0fa3ef746",
    "details": null,
    "error": null
}

Switching networking from private to public if there is a policy preventing public IP causes unrecoverable failure

Not sure if this is the correct place to report issues, but it's the only place I could find.

When switching Synapse to public networking, you would expect the API Call to fail with a policy violation if public IPs are not allowed. Instead, Synapse accepts the change, goes to a failed provisioning state, and then all further updates to Synapse fail due to

The workspace is in a nonterminal state Failed and cannot be updated (Code: WorkspaceInNonTerminalState)

This is quite dangerous as it means any person with Contribute access to the subscription can irreparably break Synapse forcing us to reprovision the entire thing, update private endpoints, etc. I have seen a support issue where someone contacts MS support to fix the failed provision state, but ideally this would not require a support call.

Any chance this issue can be addressed?