The term 'Get-SPOServicePrioritizationAppRegistrations' is not recognized as the name of a cmdlet, function, script file, or operable program

[digiofficerobin]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

PowerShell 5.1.26100.3624
Microsoft.Online.SharePoint.PowerShell 16.0.26017.12000

Describe the bug / error

Hi, I want to use the new feature Service Prioritization in SharePoint feature.

See also this video: Introduction to SharePoint service prioritization

Steps to reproduce

1. I've installed the PowerShell module Microsoft.Online.SharePoint.PowerShell 16.0.26017.12000.
2. Run command Get-SPOServicePrioritizationAppRegistrations.

I get the following error:

PS C:\WINDOWS\system32> Get-SPOServicePrioritizationAppRegistrations
Get-SPOServicePrioritizationAppRegistrations : The term 'Get-SPOServicePrioritizationAppRegistrations' is not
recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
At line:1 char:1

• Get-SPOServicePrioritizationAppRegistrations

•   + CategoryInfo          : ObjectNotFound: (Get-SPOServiceP...ppRegistrations:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  
  

Other commands like Get-SPOSite do work correctly.

Expected behavior

List of prio apps

[a1mery]

Are other cmdlets related to this feature working for you (e.g.: New-SPOServicePrioritizationBillingPolicy, Get-SPOServicePrioritizationBillingPolicies)?
Because since this feature is still rolling out, it might not be fully enabled for your tenant yet.

[Ashlesha-MSFT]

Hello @digiofficerobin,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@digiofficerobin,
yes @a1mery,
There is note in the doc,
This functionality is still rolling out and might not be fully enabled on your tenant yet.

[digiofficerobin]

@Ashlesha-MSFT Oke, I have seen that, but does that mean that the PowerShell commands are also not available? I've updated the PowerShell module on my local machine, but that won't get me the newer commands.

How can we (let) enable this feature on our tenants? We are in need for this feature.

@a1mery I get the same error message: The term 'Get-SPOServicePrioritizationBillingPolicies' is not recognized
as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.

[killerewok2000]

Hi all, we are aware of the error that is why we have added this note. The feature had paused on roll out due to last minute marketing and platform adjustment but will try to update here when we have an ETA to update the module and roll out.

[killerewok2000]

just wanted to let everyone know that the server piece is live and rolled out. only remaining piece still pending is for the PowerShell module to release its next iteration (normally monthly and should be released next week)

https://www.powershellgallery.com/packages/Microsoft.Online.SharePoint.PowerShell/