GSA known limitations

This page's changes and edits · All guidance changes

Microsoft's edit · 30 Sep 05:00 UTC

Merge pull request #14492 from cagautham/docs/update-gsa-macos-secure-dns

Microsoft's commit message in MicrosoftDocs/entra-docs · commit 1ca14c7 · +1 −6 lines · also on GitHub

⋯ 271 unchanged lines

272272 - The Global Secure Access client doesn't support multi-session Azure Virtual Desktop.

273273

274274 ## Global Secure Access In Government Cloud limitations

275 −Global Secure Access is not available in the US Government community cloud High (GCC-H), Department of Defense cloud and other Govt/Sovereign cloud environments.

276 −

277 −For usage in US Government community (GCC) cloud, known limitations/disclaimers include:

278 −

279 −- Non Federal Information Processing Standard (FIPS) 140-2 certified: Note that while the GSA service is FedRAMP High accredited, it is not yet FIPS 140-2 certified. Microsoft is actively working toward achieving FIPS accreditation/certification, and this process is currently underway. Customers should consider this status when evaluating compliance requirements. FIPS 140-2 is a US government standard that defines FedRAMP minimum security requirements for cryptographic modules in products and systems. For more information, see [Federal Information Processing Standard (FIPS) 140](/azure/compliance/offerings/offering-fips-140-2).

280 −- Data Residency Requirements: Customers should carefully consider data residency requirements when evaluating the GSA solution for their needs. When using GSA, there is a possibility that your data (up to and including customer content) may be Transport Layer Security (TLS) terminated and processed outside the United States esp. in cases where the users access GSA while traveling outside of the USA and its territories. Additionally, data may also be TLS terminated and processed outside of the USA when GSA routes traffic through the nearest available edge location, which may be outside USA borders depending on several factors. Factors for TLS termination and processing outside the US may include but not limited to: user’s physical location, proximity to edge locations, network latency, service availability, performance considerations, customer configurations and so on. As an example, a user near a USA border with a non-USA region may connect to a non-USA edge, where data inspection and policy enforcement take place.

275 +Global Secure Access is available in the US Government Community Cloud (GCC), but isn't yet supported in the US Government Community Cloud High (GCC-H), Department of Defense cloud, or other government or sovereign cloud environments.

281276

282277 ## Explicit Forward Proxy (preview) limitations

283278 Known limitations for Explicit Forward Proxy (preview) include:

⋯ 8 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 22:20 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.