Thanks for posting your question in the Microsoft Q&A forum.
This is a common problem when trying to establish peering between virtual networks that exist in different subscriptions or Azure Active Directory tenants.
- Ensure that the user account you're using has the necessary permissions in both subscriptions. At minimum, you need the "Network Contributor" role for the virtual networks in both subscriptions
- If the virtual networks are in different AD tenants, first add the user from each tenant as a guest in the opposite tenant, then assign the
Network Contributor
role to the guest user for the relevant virtual network in each tenant - If you're unable to use a single account with permissions in both subscriptions, consider using an account in each subscription with the proper permissions to create the virtual network peering
- If you're using Azure CLI or PowerShell, ensure you're logged in with the correct account and that your access token is valid
In some cases, there might be denial assignments preventing the peering action. Review any existing denial assignments and remove them if necessary
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful