Describe effect of "Allow Azure Services and resources to access this workspace"

[fmms]

This documentation should explain what exactly is meant by the checkbox Allow Azure Services and resources to access this workspace .

This can be easily confused with Allow Azure services on the trusted services list that is available on the storage account.

To my understanding:

• trusted services for a storage account are just within a subscription
• Azure Services on an Azure Synapse workspace, give ALL Azure IP ranges from ALL regions for ALL services access to the Synapse SQL endpoint

This is a significant difference that should be explained.

Thanks

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 27b4ec3e-3d82-258b-2038-2990c9f24479
• Version Independent ID: 6c0a6b2e-3b3a-bbd4-8262-fe2c82bd9402
• Content: Configure IP firewall rules - Azure Synapse Analytics
• Content Source: articles/synapse-analytics/security/synapse-workspace-ip-firewall.md
• Service: synapse-analytics
• Sub-service: security
• GitHub Login: @ashinMSFT
• Microsoft Alias: seshin

[himanshusinha-msft]

Thanks for the ask . At this time we are reviewing the ask and we will reply back as soon as we can .

[himanshusinha-msft]

We have assigned the issue to the content author . They will evaluate & update the document as appropriate. @julieMSFT : Can you please help and assign this to the correct author ?

[julieMSFT]

reassign:ashinMSFT

[PRMerger18]

ashinMSFT is not a valid GitHub ID, or is not a collaborator on this repo.

[julieMSFT]

reassign:alexshinmsft

[PRMerger10]

alexshinmsft is not a valid GitHub ID, or is not a collaborator on this repo.

[julieMSFT]

reassign:RonyMSFT

[julieMSFT]

@RonyMSFT Please look into this Gi issue.

[bandersmsft]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close