Explanation:
Box 1: Create a replicate on the same logical server.
A High Availability (HA) replica uses the same page servers as the primary replica.
A named replica, just like an HA replica, uses the same page servers as the primary replica.
Box 2: Add an ApplicationIntent entry to the connection string.
Connecting to an HA replica.
In Hyperscale databases, the ApplicationIntent argument in the connection string used by the client dictates whether the connection is routed to the read-write primary replica or to a read-only HA replica. If ApplicationIntent is set to ReadOnly and the database doesn't have a secondary replica, connection will be routed to the primary replica and will default to the ReadWrite behavior.
Example:
-- Connection string with application intent
Server=tcp:<myserver>.database.windows.net;Database=<mydatabase>;ApplicationIntent=Read Only;User ID=<myLogin>;Password=<myPassword>;Trusted_Connection=False; Encrypt=True;
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale-replicas?view=azuresql&tabs=tsql
https://sqlserverguides.com/read-only-replica-azure-sql/