Azure Key vault api's return a 401 when the resource is https://vault.azure.net/
The Azure key vault data plane API does not work when the signing resource is https://vault.azure.net/ and works fine with https://vault.azure.net . This seems to be pretty lame as only a forward slash should not make that much of a difference.
The other resource such as management.azure.com works pretty fine with the forward slash
Thuan Soldier commented
Per my test it is correct!