GSA deployment planning
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit c0359e9 · +4 −1 lines · also on GitHub
⋯ 22 unchanged lines
2323
2424
## Perform a Proof of Concept
2525
26
−Perform a [Proof of Concept](https://aka.ms/globalsecureaccesscommunity) (PoC) to ensure that the solution you choose provides the features and connectivity that you require.
26
+Perform a [Proof of Concept](gsa-poc-guidance-intro.md) (PoC) to ensure that the solution you choose provides the features and connectivity that you require.
2727
2828
Depending on which capabilities you plan to deploy in a PoC for Microsoft Global Secure Access, you need up to seven hours. Ensure you have met the [licensing requirements](../global-secure-access/overview-what-is-global-secure-access.md#licensing-overview).
2929
⋯ 250 unchanged lines
280280
- [Microsoft Global Secure Access Deployment Guide for Microsoft Entra Private Access](gsa-deployment-guide-private-access.md)
281281
- [Simulate remote network connectivity using Azure Virtual Network Gateway - Global Secure Access](../global-secure-access/how-to-simulate-remote-network.md)
282282
- [Simulate remote network connectivity using Azure vWAN - Global Secure Access](../global-secure-access/how-to-create-remote-network-vwan.md)
283
+- [Introduction to Global Secure Access Proof of Concept Guidance](gsa-poc-guidance-intro.md)](gsa-poc-guidance-intro.md)
284
+- [Global Secure Access Proof of Concept Guidance - Configure Microsoft Entra Private Access](gsa-poc-private-access.md)
285
+- [Global Secure Access Proof of Concept Guidance - Configure Microsoft Entra Internet Access](gsa-poc-internet-access.md)
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 10 Oct 07:51 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.