Feature Request

### Community Note

- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment

### Description

#### Is your feature request related to a problem?

I am unsure whether its a feature request or bug. Let me describe the problem we are seeing.

as per microsoft documentation, Azure AI services has three possible endpoints, https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns

Private link resource type | Subresource | Private DNS zone name | Public DNS zone forwarders
-- | -- | -- | --
Azure AI services (Microsoft.CognitiveServices/accounts) | account | privatelink.cognitiveservices.azure.com privatelink.openai.azure.com privatelink.services.ai.azure.com | cognitiveservices.azure.com openai.azure.com services.ai.azure.com

Cognitive account of type "OpenAI" for example gets endpoint openai.azure.com where as FormRecognizer endpoint is cognitiveservices.azure.com

since the policy is looking at privateLinkServiceId and groupIds to identify target dns, this is same for all cognitive accounts. And as things stand, when a private endpoint for an openai service is created, policy will associate this endpoint with domain cognitiveservices.azure.com where as it should be associated to openai.azure.com

Is the right approach is to deploy dns records for all dns zones like the way policy 437914ee-c176-4fff-8986-7e05eb971365 does?

policy set: Deploy-Private-DNS-Zones

#### Describe the solution you'd like

It would be great if policy set is compliant to dns mapping provided in azure private dns endpoints mentioned in https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns

#### Additional context

Read the Deploy-Private-DNS-Zones policy set and compare it with policy 437914ee-c176-4fff-8986-7e05eb971365. Use the Microsoft private endpoint DNS mapping to check how OpenAI and FormRecognizer endpoints are associated. Done means the policy set follows the documented mappings for the relevant Azure AI service DNS zones.

Written by the indexing model from the issue text.