Private DNS Zone Group return 404

### Description

For dnszonegroups that were newly created, we are getting reports of dns zone groups returning 404

### Issue script & Debug output

Azure backup runs daily tests for its private endpoint creation and DNS zone integration using powershell in canaries.
We are using New-AzPrivateDnsZoneGroup commandlet to associate private endpoint and private dns zone.

```PowerShell
New-AzPrivateDnsZoneGroup -ResourceGroupName $VaultResourceGroupName -PrivateEndpointName $privateEndpointName -Name "default" -PrivateDnsZoneConfig @($vaultPrivateDnsZoneConfig, $blobPrivateDnsZoneConfig, $queuePrivateDnsZoneConfig) -Force -ErrorAction Ignore
```

Before 6th January this used to exist by default, but is now throwing 404
```
HttpIncomingRequests
| where targetResourceProvider contains "Microsoft.Network"
| where targetUri contains "mercuryofficialpeccy"
| where authorizationAction startswith "Microsoft.Network/privateEndpoints/privateDnsZoneGroups"
| where subscriptionId == "60176b39-43ab-44f7-9ab2-7bbbb0edc829"
| where TIMESTAMP >= datetime(2023-01-02T03:00:19Z) and TIMESTAMP <= datetime(2023-01-10T03:59:19Z)
| project TIMESTAMP, subscriptionId, authorizationAction, httpMethod, targetUri, httpStatusCode

TIMESTAMP authorizationAction targetUri httpStatusCode
2023-01-05 03:26:07.8963070 Microsoft.Network/privateEndpoints/privateDnsZoneGroups/read https://management.azure.com:443/subscriptions/60176b39-43ab-44f7-9ab2-7bbbb0edc829/resourceGroups/mercuryofficialpeccy/providers/Microsoft.Network/privateEndpoints/CVT638084851880098857conn/privateDnsZoneGroups/default?api-version=2022-05-01
200
2023-01-05 03:26:08.6255186 Microsoft.Network/privateEndpoints/privateDnsZoneGroups/write https://management.azure.com:443/subscriptions/60176b39-43ab-44f7-9ab2-7bbbb0edc829/resourceGroups/mercuryofficialpeccy/providers/Microsoft.Network/privateEndpoints/CVT638084851880098857conn/privateDnsZoneGroups/default?api-version=2022-05-01
201
2023-01-05 03:26:19.0290570 Microsoft.Network/privateEndpoints/privateDnsZoneGroups/read https://management.azure.com:443/subscriptions/60176b39-43ab-44f7-9ab2-7bbbb0edc829/resourceGroups/mercuryofficialpeccy/providers/Microsoft.Network/privateEndpoints/CVT638084851880098857conn/privateDnsZoneGroups/default?api-version=2022-05-01
200
2023-01-06 03:25:23.8123412 Microsoft.Network/privateEndpoints/privateDnsZoneGroups/read https://management.azure.com:443/subscriptions/60176b39-43ab-44f7-9ab2-7bbbb0edc829/resourceGroups/mercuryofficialpeccy/providers/Microsoft.Network/privateEndpoints/CVT638085714912873194conn/privateDnsZoneGroups/default?api-version=2022-05-01
404
2023-01-07 03:17:06.8151289 Microsoft.Network/privateEndpoints/privateDnsZoneGroups/read https://management.azure.com:443/subscriptions/60176b39-43ab-44f7-9ab2-7bbbb0edc829/resourceGroups/mercuryofficialpeccy/providers/Microsoft.Network/privateEndpoints/CVT638086575185120348conn/privateDnsZoneGroups/default?api-version=2022-05-01
404
```

Since the command is to create the private dns zone group, should it not create the group, if not present.
Our tests are failing daily due to this. Since this private dns zone group is not created, DNS resolution fails and calls to all out services are failing.

### Environment data

```PowerShell
n/a
```

### Module versions

```PowerShell
n/a
```

### Error output

```PowerShell
n/a
```