Microsoft.Network/frontdoors/frontendEndpoints/customHttpsConfiguration: Does not have types available (but deployment succeeds).

### Resource Type

Microsoft.Network/frontdoors/frontendEndpoints/customHttpsConfiguration

### Api Version

2020-07-01

### Issue Type

Type is unavailable

### Other Notes

Says that types are not available, but deployment works fine.

### Bicep Repro

resource customHttpsConfiguration 'Microsoft.Network/frontdoors/frontendEndpoints/customHttpsConfiguration@2020-07-01' = {
parent: azureFrontDoor::frontendEndpoint
name: 'default'
properties: {
protocolType: 'ServerNameIndication'
certificateSource: 'FrontDoor'
frontDoorCertificateSourceParameters: {
certificateType: 'Dedicated'
}
minimumTlsVersion: '1.2'
}
}

### Confirm

- [X] I have read the troubleshooting guide and looked for duplicates.

Start by locating the type definitions for Microsoft.Network/frontdoors/frontendEndpoints/customHttpsConfiguration at API version 2020-07-01 and compare them with the supplied Bicep repro. Verify the resource and its properties are represented so the declaration no longer reports unavailable types while the deployment remains valid.

Written by the indexing model from the issue text.