![]() ![]() function Get-M365LicenseFriendlyName | Select-Object -ExpandProperty "Service_Plans_Included_Friendly_Names") -join ' ') More information on M365 licensing service plans can be found here. Anyhow, I ended up shoving it into a function to be a little easier to reuse. If you’re reading this later, and Microsoft moved the file, don’t hate me for the broken link. The interesting thing is that, as of today at least, the mapping of SKU data to descriptive names is maintained in a CSV file posted here. Getting purchases approved is super easy these days. This came from a client request where we had already set up a daily report showing their various license counts, so they can start begging, oops, I mean, requesting purchase of more licenses to stay ahead of new hires. The URL in the code example below has been updated. This will happen each time the file is updated/replaced by Microsoft. UPDATE 3/29/22 – The CSV file was updated on 3/23/22, so the previous URL is no longer valid. Using PowerShell to Improve M365 License Descriptions If not, it’ll join a long list of composted material feeding stray animals somewhere. I haven’t had many concise thoughts lately about things to complain about, so I thought I’d just share some semi-arranged meanderings of a quasi-organized set of “recent” experiences.
0 Comments
Leave a Reply. |