Update concept-dev-box-network-requirements.md

[ri-we]

The recommendation, of using the service tag AzureCloud do not make any sense from a security perspective. Allowing all IP's in Azure? It's includes also the hackers IP. The service tag Internet can't be used on the firewall.

[prmerger-automator]

@ri-we : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 5c6f542:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/dev-box/concept-dev-box-network-requirements.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@RoseHJM

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[RoseHJM]

Hi @ri-we, thank you for your comments. I will consult with the product group and make the appropriate updates.

[ri-we]

Hello @RoseHJM, thanks. This isn't the only Microsoft product documentation that uses overly broad service tags. These tags don't align with the Secure Future Initiative. Why aren't there more product-specific service tags or FQDN tags, or even a Microsoft namespace that isn't shared with Azure, like the new Microsoft Defender for Endpoint URLs (e.g., *.endpoint.security.microsoft.com)?