Task 03: Configure Enhanced Telemetry
DOCUMENT CATEGORY: Runbook SCOPE: Configure diagnostic level, streaming data client, and EU location settings f... PURPOSE: Configure diagnostic level, streaming data client, and EU location settings for Azure Local telemetry MASTER REFERENCE: Azure Local Telemetry and Diagnostics
Status: Active
Enhanced telemetry settings enable comprehensive diagnostics, proactive support, and real-time monitoring for Azure Local clusters.
Overview
Telemetry configuration includes three key settings:
- diagnosticLevel: Controls the amount of diagnostic data sent to Microsoft
- streamingDataClient: Enables real-time streaming of telemetry data
- isEULocation: Configures EU data residency compliance
Prerequisites
- Azure Local cluster registered with Azure Arc
- Owner or Contributor role on the cluster resource
- Understanding of data privacy requirements
- Knowledge of data residency requirements (EU vs non-EU)
Values from infrastructure.yml
The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.
Execution Options
- Azure Portal
- Orchestrated Script
Steps
- Navigate to the Azure portal → Azure Arc → Azure Local
- Select your cluster resource
- Go to Settings → Configuration
- Locate the Diagnostics section
- Configure the following settings:
- Diagnostic Level: Select
EnhancedorFull - Streaming Data: Toggle to Enabled
- EU Data Boundary: Set based on cluster location
- Click Save
Diagnostic Levels
| Level | Data Sent |
|---|---|
| Required | Minimum data for cluster health |
| Enhanced | Additional data for proactive support |
| Full | Complete diagnostics for troubleshooting |
PowerShell
No script in this task folder.
Invoke-TelemetryConfiguration-Orchestrated.ps1is a placeholder: it printsNOT IMPLEMENTED, changes nothing and exits with code 3. The task has no Azure CLI script: Microsoft Learn documents the diagnostic data settings only as deployment settings. The earlierSet-TelemetryConfiguration.ps1is removed: Microsoft Learn documents no supported way to do what it did. The deployment sets the diagnostic data fromsecurity.telemetryofinfrastructure.yml(streaming_data,episodic_data_upload,eu_location).
Diagnostic Level Details
Basic (Required)
- Cluster health status
- Node connectivity information
- Critical error reporting
- Minimum data for Azure billing
Enhanced (Recommended)
- All Basic data plus:
- Performance metrics
- Feature usage statistics
- Proactive issue detection
- Support case acceleration
Full (Troubleshooting)
- All Enhanced data plus:
- Detailed diagnostic logs
- Memory dumps (on request)
- Complete event logs
- Deep troubleshooting capability
EU Data Boundary
For clusters deployed in European Union member states:
# Enable EU data boundary on the cluster
Set-AzStackHCI -IsEULocation $true
# This ensures:
# - Telemetry data stays within EU boundaries
# - Compliance with GDPR requirements
# - Data processed in EU Azure regions
Verification
# On the cluster node
Get-AzStackHCI | Select-Object DiagnosticLevel, StreamingDataClient
# Verify telemetry service
Get-Service -Name "HciClusterAgentService" | Select-Object Status, StartType
# Check telemetry connectivity
Test-NetConnection -ComputerName "dc.services.visualstudio.com" -Port 443
Troubleshooting
| Issue | Resolution |
|---|---|
| Telemetry not sending | Verify firewall allows HTTPS to telemetry endpoints |
| Streaming data failing | Check HciClusterAgentService is running |
| EU setting not applying | Verify cluster region is set correctly |
| Diagnostic level reset | Re-apply after cluster updates |
Telemetry Endpoints
Ensure firewall allows outbound HTTPS (443) to:
dc.services.visualstudio.com*.applicationinsights.azure.com*.monitor.azure.com*.blob.core.windows.net
Related Documentation
Scripts for this task are located in the azurelocal-toolkit repository under scripts/deploy/ in the appropriate task folder.
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Navigation
| Previous | Up | Next |
|---|---|---|
| ← Task 02: Windows Server Subscription | Phase 05: Licensing & Telemetry | Part 06: Testing & Validation → |
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2026-03-24 | Azure Local Cloud | Initial release |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2025-03-25 | Azure Local Cloud | Initial release |