GSA deployment planning
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 6bbd395 · +1 −1 lines · also on GitHub
⋯ 24 unchanged lines
2525
2626
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.
2727
28
−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#licensing-overview.md).
28
+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
3030
- Configure prerequisites: One hour
3131
- Configure initial product: 20 minutes
⋯ 253 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 10 Oct 07:51 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.