Most likely the egress policy change hasn’t actually taken effect on the serverless compute that’s running your notebook.

Check these things in order:

1. Verify the network policy itself (Account Console → Security → Networking → Context-based ingress & egress):

   • On the Egress tab, confirm the policy is set to “Allow access to all destinations” (not restricted).
   • Confirm that this policy is associated with your workspace (Network Policy column for that workspace).

2. Restart serverless compute so it picks up the new policy:

   • Stop all serverless clusters / all-purpose compute attached to the workspace, then start a new serverless cluster and re-attach your notebook.
   • Internet-access mode changes only take effect after this restart and can otherwise lag up to 24 hours.

3. Retest from the fresh session:

   import requests
   requests.get("https://api.hubapi.com").status_code
   

4. If it still fails, check denial logs:

   SELECT *
   FROM system.access.outbound_network
   WHERE host ILIKE '%hubapi.com%' OR host ILIKE '%google.com%'
   ORDER BY event_time DESC
   LIMIT 100;
   

   • If you see DROP entries, your egress/firewall config is still blocking; share this query output in a Databricks support ticket.
   • If there are no entries for those hosts, open a support ticket with your workspace ID and a failing notebook run ID so platform can investigate.