Medium risk
Upload examples explicitly overwrite an existing remote blob
Source references: 3What we found
Several quick-start examples set the overwrite option to true. If a blob with the same name already exists, running them replaces its content with the example data.
Why this matters
Existing Azure data could be lost or corrupted. Recovery depends on whether blob versioning, soft delete, or backups are enabled.
This is example code and does not run merely because the Skill is installed. However, if a user runs it after replacing the placeholders with a real account, both the Python and C# examples explicitly permit overwriting. An existing blob with the same name would be replaced by the sample data. Before running it, verify the account, container, and blob name, and allow overwrite only when explicitly intended.
service = BlobServiceClient(account_url="https://ACCOUNT.blob.core.windows.net/", credential=DefaultAzureCredential())container = service.get_container_client("my-container")blob = container.get_blob_client("my-blob.txt")blob.upload_blob(b"Hello, Azure Storage!", overwrite=True)```Show 2 other places
var client = new BlobServiceClient(new Uri("https://ACCOUNT.blob.core.windows.net/"), new DefaultAzureCredential());var container = client.GetBlobContainerClient("my-container");var blob = container.GetBlobClient("my-blob.txt");await blob.UploadAsync(BinaryData.FromString("Hello, Azure Storage!"), overwrite: true);``` .buildClient();BlobContainerClient container = client.getBlobContainerClient("my-container");BlobClient blob = container.getBlobClient("my-blob.txt");blob.upload(BinaryData.fromString("Hello, Azure Storage!"), true);```