Acz safe scripts clean (#316752)
* Replace automated script with manual GET/PUT/Verify approach in Step 3
- Removed automated Bash/PowerShell scripts
- Added Step 3.1: Get current configuration (preserves all properties)
- Added Step 3.2: Update with managed identity (uses placeholders for paste)
- Added Step 3.3: Verify managed identities attached
- Added WARNING about PUT replacing entire config (prevents Incident 806245084)
- Updated API version to 2025-12-15
- Simplified approach reduces maintenance burden
* Update Step 4 to require both users and users.datalake.viewers groups
- Updated requirement to include users.datalake.viewers@{data-partition-id}.dataservices.energy
- Added verification commands for both entitlement groups
- Updated sample response text to reflect both groups
* Fix Acrolinx issues: present tense, substeps, and contractions
- Changed 'will delete' to 'deletes' (present tense)
- Changed 'sub-steps' to 'substeps' (consistency)
- Changed 'they will' to 'they'll' (tone/contractions)
* Fix Acrolinx: use present tense for appear
- Changed 'they'll also appear' to 'they also appear'
* Add placeholder tables to Step 3 substeps
- Added placeholder table to Step 3.1 explaining subscription-id, resource-group, and adme-instance-name
- Added placeholder table to Step 3.2 explaining all placeholders including managed-identity-resource-id and paste instructions
- Improves consistency with other steps in the document
* Add placeholder table to Step 3.3 for consistency
- Added placeholder table explaining subscription-id, resource-group, and adme-instance-name
- Added NOTE that variables are already set if running in same terminal session
- Completes placeholder table coverage for all Step 3 substeps
* Fix Acrolinx: Change 'GET response' to 'response from Step 3.1'
- Removes HTTP method from prose for better clarity
- Fixes 4 occurrences in Step 3.2 placeholder table
* Fix PowerShell script issues in Step 3
- Add backtick escape before ?api-version in Steps 3.1 and 3.2 (PowerShell requires backtick before ? in double-quoted strings)
- Add \ and \ variable definitions to Step 3.3 for standalone execution
- Ensures Step 3.3 works even when not run in same terminal session as 3.1/3.2
Resolves testing feedback from Amita's validation
* Add variable definitions to Step 3.3 bash script
- Add SUBSCRIPTION_ID, RESOURCE_GROUP, ADME_INSTANCE_NAME variable definitions
- Add TOKEN generation command
- Ensures Step 3.3 bash script works standalone like PowerShell version
- Completes parity between bash and PowerShell scripts
* Revert "Update Step 4 to require both users and users.datalake.viewers groups"
This reverts commit 41f96113c8b86e47e24ec5d403b9aabeeb9a2cc7.
* Fix Step 3.1 to display full JSON without truncation
- Changed from 'Get-Content adme-config.json | ConvertFrom-Json' to 'Get-Content adme-config.json'
- ConvertFrom-Json causes PowerShell to truncate nested objects
- Users need to see full JSON to copy values for Step 3.2
- Added TIP note explaining users will need this data for Step 3.2
Fixes issue where identity, properties, and tags were truncated as @{}
* Fix Acrolinx: Change 'you'll need' to 'you need' (future to present tense)
* Fix bash scripts: Add | tr -d '\r' to TOKEN lines for WSL compatibility
- All bash scripts failed on Windows/WSL due to line ending issues
- Azure CLI in WSL outputs CRLF, adding trailing \r to TOKEN
- Azure ARM API rejects tokens with trailing whitespace (HTTP 400)
- Applied fix to all 3 bash TOKEN assignments:
* Step 3.1 GET configuration
* Step 3.2 PUT update
* Step 3.3 Verify managed identity
- PowerShell scripts already work (no line ending issues)
- Tested and validated all scripts working
* Add provisioning state wait requirement to Step 3.3 verification
* Trigger rebuild
* Fix malformed character in Step 4: storage—it