Get-MgSubscribedSku outputs a SkuPartNumber with extra characters

[bbrownchg]

When running Get-MgSubscribedSku to grab all licenses available in my tenant, an extra, unknown, character is getting appended to the end of the CPC_E_2C_8GB_128GB SkuPartNumber.

In the console output of Get-MgSubscribedSku | Select-Object SkuPartNumber there is no obvious extra character, as seen below:

Exporting the results to CSV shows something being added on to the end:

Running Get-MgSubscribedSku | where {$_.skupartnumber -eq "CPC_E_2C_8GB_128GB"} returns no results, whereas Get-MgSubscribedSku | where {$_.skupartnumber -like "CPC_E_2C_8GB_128GB*"} does return an object.

Running the same query using an HTTP call via https://graph.microsoft.com/v1.0/subscribedSkus does not appear to show the extra character.

Based on this incorrectly filed issue, https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8606, the extra character was identified as a zero-width space.

This is causing issues with matching SKU names to friendly names in automation scripts.

[SeniorConsulting]

Hi bbrownchg,

Did this just affect the Cloud PC license? i.e. CPC_E_2C_8GB_128GB?

I've conducted some testing, and have found that the other ones seem to be OK:

However, I have replicated this issue on the Cloud PC SKU:

I think this may actually be a service issue, rather than an issue with the module

FYI - this also seems to affect the other Cloud PC SKU:

[SeniorConsulting]

Confirmed that it's a service issue via the debug command!

[bbrownchg]

Confirmed that it's a service issue via the debug command!

I see that now, good catch. Doing the HTTP call and converting to JSON also shows me the extra character that I wasn't seeing before using the Graph Explorer.

Hopefully someone can help us get this logged to the correct team!

[peombwa]

Thanks @SeniorConsulting for helping identify the root cause of the issue!

@bbrownchg, please open a ticket at https://developer.microsoft.com/graph/support with the request-id and date of the affected request as this is an issue with the service returning incorrect results. See https://learn.microsoft.com/powershell/microsoftgraph/troubleshooting?view=graph-powershell-1.0#using--debug.

[bbrownchg]

Thank you, @peombwa. I have opened a case in my Azure subscription, ID 2309260040011228 if it helps.

[peombwa]

Awesome! Closing the issue in the repo as this is an issue with the service, not the SDK.

[bbrownchg]

FYI for @peombwa @SeniorConsulting and anyone else that happens to find this thread, MS support got back to me with unfortunate news:

Hi Brandon,
The Product Group was able to identify where the extra characters come from. Unfortunately they would not be able to take a fix for this since it would impose a huge compatibility risk. Due to the way it’s designed, the part number is immutable in all systems since it directly ties to the services on these product SKUs. They can not be changed or the customers who have purchased these will break. This behavior has been in market for over 2 years. The product group advised whichever system can’t handle these characters is going to need to make adjustment to handle them.