Our team has tens of developers who have MSDN account. We'd like to share same VNet which connects to our on-premise network.
Each developer has free-tier Azure usage within their MSDN account, but they can not start virtual machines in the on-premise-connected VNet using the free tier.
To start virtual machines with their account and to access them from on-premise network, It seems that they have to make their own VNet and connect it to the on-premise-connected VNet. It is not convenient.
I believe that If the owner of the on-premise-connected VNet could allow other accounts to create virtual machines within the VNet, lots of developers will be happy for that.
Virtual Network scope is restricted to a subscription for manageability.
tamagawa ryuji commented
Thank you for your comment Erik,
I know what you mean. Actually, what I want to do is that:
Let's say we have developer A and B, and both of them have free tier from thier MSDN subscription. A has a VNet connected to on-premise network. B want to use virtual machines in A's VNet under his/her free tier.
You have to associate your MSDN accounts with your Organizational account in your MSDN profile page, this allows the users to log in with their AD credentials and gain access to AD managed subscription resources I believe.