@Anonymous Thank you for reaching out.
You can configure the GeoReplicated secondary as a serverless database. The primary database should be in a vCore pricing model.
Although technically possible, the general recommendation is to have both primary and secondary databases on the same service tier.
If the primary database is experiencing a heavy write workload, a secondary with lower compute size may not be able to keep up with it.
That will cause redo lag on the secondary, and potential unavailability of the secondary. To mitigate these risks, active geo-replication will throttle the primary's transaction log rate if necessary, to allow its secondaries to catch up.
More on this topic is here
Please let us know if you have any further questions.
----------
If an answer is helpful, please "Accept answer" or "Up-Vote" for the same which might be beneficial to other community members reading this thread.