Forum Discussion
Visual Studio Lite benefits - without Azure Credits and Keys
- Feb 17, 2026
New benefits have been released as of February 13, 2026. Partner Blog | Expanded partner benefits are now available: What’s new in February 2026 | Microsoft Community Hub
The team also mentioned:
Refresh went live Feb 13, so any benefits packages that are available to purchase now will reflect that. Note that the changes are retroactive, except for changes to Microsoft Visual Studio.
Some other announcement links in case you find them helpful:
Explore your Visual Studio and GitHub benefits - Partner Center | Microsoft Learn
Microsoft AI Cloud Partner Program: Key updates to developer benefits and Visual Studio access
Manage Microsoft AI Cloud Partner Program benefits - Partner Center | Microsoft Learn
Thank you for your feedback as well!
Unfortunately, contrary to what the article states, this is a downgrade. Lack of dev/test downloads and keys is a huge loss and makes the whole benefit package significantly less valuable. Being able to create lab and dev environments to test in is critical. Renaming the product so it doesn't sound as inferior did not change the fact that it is. Please reconsider this.
KolbyG thank you for your feedback, I will share it with the team.
Please be aware that we can share feedback we receive, but it doesn't always mean they will utilize it, just to set your expectations. ⭐
- felixc7Feb 21, 2026Copper Contributor
Honestly: the fact that in all the communication and announcements Microsoft refuse to call it what it is: a significant downgrade in value - makes me almost more angry than losing the benefit itself. Saying no, no, there is no loss as we added value X and value Y is ridiculous. First of all it doesn't add up in raw numbers and secondly having e.g. the "benefit" of 35 Dragon Copilots Licences in every package and calling it an adequate value add is like taking the best knive of a chef and giving him a stethoscope instead. There would have been a middle ground. E.g. we never used all the Visual Studio Enterprise Licences and I didn't assigned it to all of my team just to have all the licences assigned. I was always hesitant because I knew you have to be careful e.g. if a member of our team is misunsing the licences there could be a potential problem losing the partner status all together. So a good middle ground would have been to reduce the total number of Visual Studio Enterprise licences. But having no way to build up a lab environment - be it on premise or on Azure - for partners is problematic to say at least. Yes. I do understand, you can also buy the MSDN package for the team members which need the ability and for at least two team members of my staff there will be no way around but buying additional licences and adding yet another few thousands to our MS costs. But at least stop telling us that your intend was instead to add value. That's not the way communication works in a healthy partnership based on mutual respect.