Azure / Azure/azure-powershell

[Feature]: New-AzSqlDatabaseExport the resulting bacpac file is not encrypted

Open
#19,159 4 comments 0 reactions 0 assignees View on GitHub
act-codegen-extensibility-squad customer-reported feature-request Service Attention SQL
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
3d 14h
Merged PRs (30d)
54

Description

### Description of the new feature

When using New-AzSqlDatabaseExport the resulting bacpac file is not encrypted. My requirement is that the bacpak file be encrypted on blob storage in case someone gains access to the blob storage or keyvault.

### Proposed implementation details (optional)

Add new encryption key parameter and use aes/pgp to encrypt the bacpak file as [filename].bacpak.encrypted

Contributor guide

Open the contributing guide

Research direction

Start at the New-AzSqlDatabaseExport cmdlet implementation and trace how the bacpac is written to Blob Storage. Clarify the encryption-key parameter and AES or PGP approach before proceeding; done means the exported bacpac is encrypted at rest and the resulting filename follows the requested encrypted form.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, powershell
Domain
cloud, databases, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.