Azure / Azure/azure-powershell
Action Required: File Blocked - take action to protect the sensitive data found in a file you modified: Microsoft.Azure.PowerShell.Cmdlets.Compute.dll-Help
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 54
Description
### Description
After every upgrade to the latest version of Azure PowerShell, a warning email is triggered with the subject:
Fw: Action Required: File Blocked - take action to protect the sensitive data found in a file you modified: **Microsoft.Azure.PowerShell.Cmdlets.Compute.dll-Help**
I suspect that sensitive information, such as Subscription IDs or Account IDs, may be embedded within the Azure PowerShell help files. This causes compliance or data protection scanning tools to flag the file during each upgrade.
Please investigate and remove or replace any sensitive information contained in:
Azure.PowerShell.Cmdlets.Compute.dll-Help
Otherwise, the warning email will continue to be triggered after every subsequent upgrade.
This needs your attention - sensitive data blocked
In collaboration with Purview Data Security, Compliance and Governance team, Microsoft is using Purview Information Protection sensitive data detection tool, which has built-in functionality to help alert and protect you and Microsoft from inadvertent oversharing or accidental exposure to sensitive data in XX for Business.
### Issue script & Debug output
```PowerShell
Alarm emails were generated following the upgrade.
```
### Environment data
```PowerShell
Windows
```
### Module versions
```PowerShell
The Compute Module is updated every time you upgrade to the latest version.
```
### Error output
```PowerShell
```
Contributor guide
Research direction
Start by locating Azure.PowerShell.Cmdlets.Compute.dll-Help in the Azure PowerShell module and inspect how it is produced during an upgrade. Reproduce the upgrade on Windows and use the reported Purview or compliance scan to identify the flagged content. Done means the help file contains no sensitive identifiers and the warning is not triggered on subsequent upgrades.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- documentation, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100