Forum Discussion
MicrosoftUpdate to Microsoft Desktop Virtualization API v. 2023-09-05 by August 2, 2024 to avoid any impact
What's the point of using listRegistrationTokens() if there is no way to generate more than one token and have both be valid at the same time?
I've tried using the portal, PowerShell Az modules, Azure CLI, and the API directly to generate token's for the same host pool and listRegistrationTokens() only ever shows 1 token.
MicrosoftHunterW620 a host pool can only have one token. The token expires based on the date time range selected / input when created. The same token may be used for multiple deployments as long as it hasn't expired or doesn't expire during the deployment. Why would you need more than one token at one point in time? The list function is a secure and simple way to get the token during an ARM template deployment.
The function name is plural.
list tokenS.
The ability to have multiple valid tokens would be a huge benefit so they can be rolled without interruption if you have an environment where hosts are constantly being deployed but don’t want long living tokens with huge expiration times.
- JasonMasten
I agree the function name is misleading since its plural.
I generate a new token in my ARM template every time I deploy new hosts so there is never a concern. Each token has a short life of 2 hours. I'm able to add hosts at scale without any issues using one token. If I need to deploy more hosts for some odd reason after my first deployment, the second deployment will create a new token which revokes the token from the first deployment. I'm still not seeing the benefit of having multiple tokens for a single host pool. Could you describe your scenario in detail?