Possible bug in portal azure sql database deplyment cancelation

Dawid Zyrek 26 Reputation points
2022-10-31T06:59:44.597+00:00

Hi,
On portal.azure.com, when creating a copy of existing sql database (same subscription, same server), you have an option to cancel it's deployment. However after pressing 'Cancel deployment' button and getting a notification with confirmation that deployment was successfully canceled - the copy of database will still be created. That has led to some unexpected costs as copies of P1 databases were created and just sat on my subscribtion for few days until I noticed.

Is that a desired behaviour/technical limitation or is it simply a bug? If it's a bug, is it platform wide or account specific?

Steps to reproduce :

  1. Have an sql database.
  2. Go to the database overwiev, press 'Create copy', go through the wizard.
  3. During copy deployment press 'Cancel deplyment'. Wait for notification with confirmation that it was successfully canceled.
  4. In some time (depending on size of source database - mine took around an hour) canceled copy will still be created.
Azure SQL Database
{count} votes

1 answer

Sort by: Most helpful
  1. Ronen Ariely 15,091 Reputation points
    2022-11-08T05:06:48.87+00:00

    Good day @Dawid Zyrek

    Thanks for sharing the information

    This place is for discussion regarding technical questions and not for feedback

    There is a specific place where you should publish such information (BUGs and feedback) in order to pass it to the right team, which is at the feedback system. Please publish your BUG Report in the following system:

    https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0

    Remember to add as much information as you can, including screenshot if you find these helpful. You should explain how the team can reproduce the scenario so they can find the solution

    Thanks again for sharing the information and for being part of QnA the community. Please remember to close this thread once you publish the bug report in the right system

    0 comments No comments