Forum Discussion
Logan_Silliman
Microsoft
MicrosoftUpdate to Microsoft Desktop Virtualization API v. 2023-09-05 by August 2, 2024 to avoid any impact
[Recommended actions updated on July 29, 2024]
WARNING! Be mindful when using secrets in deployment templates and follow Azure best practices when managing secrets. Our examples in this d...
Logan_SillimanRegarding retrieveToken.bicep, it appears that the registration token is updated each time the module is invoked. Is it safe to execute multiple deployments with this module concurrently?
- Logan_SillimanGreat question! It depends! if this module is being invoked for different hostpools, then yes, it should be safe! If this module is invoked in parallel for the same hostpool, you will likely end up with conflicts.
The provided samples are are intended solely for educational purposes. You should adapt them to fit your production use cases: e.g. you can store the resulting hostpool registrationToken in a keyvault and have all subsequent deployments access this value from key vault.
Even better, you can start using listRegistrationTokens() function instead, which will retrieve existing tokens and won't recreate them.
JasonMastenLogan, where is the documentation for the new "listRegistrationTokens()" function?- Logan_Silliman
JasonMasten official documentation will be updated soon! For now, please follow the recommendation from this blog post. For all intents and purposes, the list API behaves the same as Host Pools - Retrieve Registration Token - REST API (Azure Desktop Virtualization) | Microsoft Learn & its documentation may be helpful in the short term.
