# Use Confluent Cloud Schema Registry to Connect to a Public Endpoint in a Private Networking Environment If you have a private networking environment and you want to use Confluent Cloud Schema Registry, you must open outbound calls (egress) to a public Schema Registry endpoint. This is because Confluent Cloud Schema Registry is a multi-tenant Schema Registry. ## Prerequisites - Confluent Cloud Schema Registry is [enabled and configured](../../get-started/schema-registry.md#cloud-sr-config). For more information about supported features, see [Manage Schemas in Confluent Cloud](../schemas-manage.md#sr-prv). - You must expose port `443` or otherwise manage a TCP-HTTPS (SSL/TLS) port forwarding scheme. This is required to access the managed Confluent Cloud Schema Registry. ## Configure Schema Registry to allow outbound calls to your private network 1. Navigate to a cluster to get to the Schema Registry settings in an environment. 2. On the information panel under **Stream Governance API**, you should see the Schema Registry endpoint. For example `https://confluent.us-east-2.aws.confluent.cloud`.  3. Open outbound calls to the Confluent Cloud Schema Registry endpoint. Follow the instructions based on your cloud provider. Azure VNet : Configure outbound call access for Azure [networking components](https://docs.microsoft.com/en-us/azure/virtual-network/). AWS VPC : Configure outbound call access for these AWS VPC networking components: - Follow the instructions in the AWS [Internet Gateway documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html). - Follow the instructions in the AWS [NAT Gateway documentation](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html). - Follow the instructions in the AWS [NAT Instance documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html). Google Cloud VPC : Configure outbound call access for Google Cloud [networking components](https://cloud.google.com/vpc/docs/vpc#internet_access_reqs). 4. Optional: Verify that your Schema Registry credentials are properly configured, where Schema Registry API key (``), API secret (``), and endpoint (``) are specified. Run this command to authenticate with the cluster and list the topics registered in your schema. ```none curl -u : \ /subjects ``` If no subjects are created, your output will be empty (`[]`). If you have subjects, your output should resemble: ```none ["test2-value"] ``` Here is an example command: ```none curl -u : \ https://psrc-lq2dm.us-east-2.aws.confluent.cloud/subjects ```