If you’ve been using the VSPC_Tenant_Resources.ps1 script, it’s worth taking another look. The version currently on main is a pretty big upgrade from the earlier release.
Heads-up: The current script was built and tested against VSPC v9.1 using REST API version 3.6.1.
Here’s what’s changed and why it actually matters.
A cleaner, more maintainable script
The original version did the job, but everything lived in one massive block of code with a lot of repeated code. The updated script breaks things out into reusable functions and helpers for things like paging API results and organizing data in memory.
That means:
-
Less duplicated code
-
Easier troubleshooting
-
Much simpler future updates
If you’ve ever tried to tweak the old version, you’ll immediately feel the difference.
Performance optimizations
Various tweaks were made to loop structures and how data is handled to significantly reduce not just lines of code or file size, but the number of APIs made to VSPC and the script execution time.
Better data, not just more data
Reporting has been tightened up across the board:
-
Usage is now pulled together more consistently for
-
BaaS
-
DRaaS
-
VB365
-
-
Previous tabs are still available but act more as a detailed inventory than something you’d give your billing team.
-
VB365 reporting is more detailed, including repositories, proxies, retention, and object storage usage.
-
Licensing now includes ownership details for backup servers, which makes life a lot easier when you’re doing audits, chargeback, or internal reporting.
Cleaner Excel output
The old script produced a lot of separate worksheets that were useful, but not always easy to consume. The new version organizes things into:
-
A consolidated Usage view (key metrics most billing departments want)
-
Dedicated sheets for BaaS, DRaaS, and VB365 details (a holistic inventory of sorts)
-
A clearer No Resources report for tenants without active services
-
More complete Licensing information
Why this update is worth your time
This isn’t just a refactor for the sake of refactoring. The new version is:
-
Easier to maintain
-
Easier to extend
-
More reliable when dealing with large environments
-
More useful for real-world reporting and billing workflows
If this script is part of how you track tenant usage or inventory today, upgrading to the latest version is well worth it.
If you haven’t pulled the updated script yet, grab it from GitHub and give it a try. And as always, if you’ve got ideas or improvements in mind, that’s exactly what the community is for.
