Private Endpoint IPv6 settings not configurable via bicep

[jesselve]

Description

Private Endpoint IPv6 settings (isIPv6EnabledPrivateEndpoint) cannot be configured through Bicep, but consistently show up as differences in what-if analysis. This leads to perpetual "changes needed" in our IaC pipelines even though the setting is not configurable through Bicep or even direct REST API calls.

Repro steps

1. Deploy private endpoints through Bicep:

   resource privateEndpoint 'Microsoft.Network/privateEndpoints@2024-01-01' = {
     name: name
     location: location
     properties: {
       privateLinkServiceConnections: [...]
       subnet: [...]
     }
   }

2. Run what-if analysis (az deployment group what-if)

3. Observe these perpetual differences:

   ~ Microsoft.Network/privateEndpoints/acme-privlink-acme-keyvault-prod [2024-01-01]
     - properties.isIPv6EnabledPrivateEndpoint: false
   

4. Attempted workarounds that didn't resolve the issue:

   • Direct REST API updates to the property
   • Different API versions
   • Explicitly setting the property in Bicep (not allowed by schema)

Expected behavior

One of these solutions:

1. Allow configuration of IPv6 settings through Bicep
2. Don't show IPv6 settings as differences in what-if when they can't be configured
3. Document that these differences should be ignored

Environment

• Bicep version: latest
• Resource type: Microsoft.Network/privateEndpoints
• API version: 2024-01-01
• Azure subscription type: Production

Additional context

• The property exists in Azure's backend state but isn't configurable through any IaC method we've found
• This affects CI/CD pipelines that rely on what-if analysis for change detection
• The differences appear benign but create noise in our deployment validation

[trylvis]

Experiencing the exact same issue.

[stephaniezyen]

Unfortunately this is a Microsoft.Network issue. Please open a support ticket with the Network RP on this to get it fixed as soon as possible.

[jesselve]

@stephaniezyen - How do I open a support ticket with the "Network RP"? Can you please help or provide a link?

[linkhuo-fha]

same issue here. the property shows in the resource json, but not configurable in bicep in different api versions.