An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
Hi @ Sindhuja Chandrasekaram,
Welcome to Microsoft Q&A Platform.
It looks like your Azure VPN client is tripping over an AADSTS650057 “Invalid resource” error—basically the client app (ID c63…cf-b95ad541b5c8) is asking for a token for resource 41b23…ed4b4, but that resource isn’t registered in the app’s API permissions.
In order for a client application to sign in and get an access token for a resource, the resource must be assigned the required API permissions that the client application requires, such as access to Azure VPN .
Ref: Verify if the resource exists in your tenant
Verify the App Registration :
Go to Azure portal > Azure Active Directory > App registrations > select your VPN client app (ID c63…cf-b95ad541b5c8). > Under “API permissions,” confirm that the resource App ID (41b23e61-6…-cd054e0ed4b4) is listed.
If it’s missing, click “Add a permission” > “My APIs” (or “APIs my organization uses”) and add the resource by its Application ID URI. >Grant admin consent for that permission.
Re-export & Import Your VPN Profile :
- After you’ve updated permissions and consented, go back to your VPN Gateway’s Point-to-Site configuration.
- Download the VPN client package again so the XML profile reflects the new resource.
- Import that fresh profile into your Azure VPN Client and retry the connection.
Please
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.