Now you add the resources (apps and web pages) that users will access through the gateway.
If you add a resource that redirects the user to a different URL after authentication or that links to other resources, add those resources too. For example, if you add wiki.mycompany.net and the wiki links to jira tickets, add jira.mycompany.net
To add resources, do as follows:
Go to Zero Trust Network Access > Resources & Access and click Add Resource.
In Add Resource, do as follows:
- Enter the resource name and description.
Check that Show resource in user portal is selected.
Specify the access type and resource details as follows:
- Select a Gateway.
- In Access method, select Agent to access the resource with the ZTNA agent or Agentless to access the resource without it. Also select the Policy to apply.
- Select the Resource type (for example, Web Application).
Enter the External FQDN and Internal FQDN/IP address of the resource, plus the port type and number (for example, HTTPS and port 443 for a web app).
If you selected agentless access, the external FQDN must be publicly available. If you selected agent access, the external FQDN must not be publicly available.
If you have an AWS gateway, set the Internal FQDN as follows:
If the app is hosted on the EC2 instance in another VPC, configure the EC2 private IP.
If the app has a custom DNS domain name, configure the private hosted zone. See Private hosted zones.
In Assign User Groups, select the available groups that need access to the resource. Move them to Assigned User Groups and select them.
If you change the name of an assigned Azure AD user group later, the list isn't updated. Users won't be able to access the app, and you'll need to assign the group again.
Check that you can access the app you added.
You can verify the SSL certificate and ensure it's the same wildcard certificate that was uploaded to the gateway.
Repeat the above steps for any other resource that this resource might redirect the user to.