In March 2024, Microsoft will depreciate the Azure AD Graph API, and in turn, the MSOnline and AzureAD PowerShell modules will be rendered useless.
Book Specification
The Xbox App has become an integral part of the Windows experience, offering seamless gaming integration, social connectivity, and a host of features for Xbox enthusiasts. However, there may be instances when you need to uninstall the Xbox App from your Windows system for troubleshooting purposes, optimizing resources, or simply personal preference.
In this comprehensive guide, we will walk you through the process of uninstalling the Xbox app from Windows 11/10 using various methods and, if you want, how to reinstall it again.
How to Remove Xbox app in Windows 10/11.
Uninstalling the Xbox app is a simple process and can be accomplished using the Start menu, the Settings app, or PowerShell.
Uninstall Xbox app using the Start Menu.
To remove the Xbox app from your Windows 11/10 system, using the Start menu:
1. Click on the Start menu and scroll through the list of installed applications until you find the Xbox app. (or just search for “Xbox” in the search bar(.
![]()
2. Then, right-click on the Xbox app and from the context menu select Uninstall. This will start the uninstall process for the Xbox app
![]()
3. Windows will display a confirmation message asking if you want to uninstall the Xbox app. Confirm your decision by clicking the Uninstall button once again. *
* After uninstalling Xbox and if you want to install it again, open the Microsoft Store, search for “xbox” and click the GET button to install it.
![]()
Remove Xbox app from Installed apps.
The second method to uninstall the Xbox app on Windows 10/11, is by using the Apps & features settings.
1. Click on the Start menu and select Settings, or alternatively, press the Windows + I keys to quickly access the settings.
![]()
2. Within the Settings, click on Apps. This will take you to the Apps & features section on Windows 10 or in Apps section on Windows 11.
![]()
3. On Windows 10, scroll down the list of installed apps until you find the Xbox app.*
* On Windows 11, click Installed Apps first and then search for the Xbox app.
![]()
4. On Windows 10, click on the Xbox app to highlight it and then click the Uninstall button.*
* On Windows 11, click the three (3) dots menu next to the Xbox app and then select Uninstall.
![]()
5. Finally click Uninstall again to confirm your decision.
![]()
6. After removing Xbox and if you want to install it again, open the Microsoft Store, search for “xbox” and click the GET button to install it.
Remove Xbox app from PowerShell.
Uninstalling the Xbox App from your Windows system can also be accomplished using PowerShell, a powerful command-line tool.
![]()
![]()
3. Wait till the process is complete. Then. type exit and press Enter to close the PowerShell window and you’re done!
![]()
How to Reinstall the Xbox App on Windows 10/11.
1. Search from “microsoft store” in search bar and open the Microsoft Store app in the results.
![]()
2. In the Microsoft Store, type xbox in the search bar located on the top. Look for the official Xbox App in the search results and click on it.
![]()
3. On the Xbox App page, click on the Get button to start the installation process of the Xbox app.
![]()
4. Once the installation is completed, you can launch the Xbox App and enjoy its features and functionalities seamlessly.
If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:
Table of Contents
No Evidence that Microsoft Cares as Pnp.PowerShell Fills the Gap

Lack of Progress with Graph API
Getting back to the PowerShell module, Microsoft has not updated it to support PowerShell 7. This might not be a problem if you always use Windows, but it does limit platform coverage. Attempting to load and use the module with PowerShell 7 usually fails, especially when multifactor authentication is involved.
The Community Approach to SharePoint Online PowerShell
Because Pnp.PowerShell is a community effort rather than something produced by Microsoft, some organizations are reluctant to use it. They fear that support for bug fixes will be limited or that some catastrophic bug will creep in due to a lack of testing. My experience is that the community developers are very responsive and do better testing than many Microsoft development groups (an example being the recent bugs afflicting the Microsoft Graph PowerShell SDK). There’s no reason to avoid using Pnp.PowerShell, subject to the normal requirements to test new versions and ensure that every cmdlet does what you expect.
Moving Forward with SharePoint Online PowerShell
Stay updated with developments across the Microsoft 365 ecosystem by subscribing to the Office 365 for IT Pros eBook. We do the research to make sure that our readers understand the technology.
💡We automated the provisioning steps in a PowerShell script for you. It will connect to our environment and get the needed changes applied to your infrastructure.
PLEASE READ BEFORE YOU START
💡 Tip: The script run is also needed when certain Service Settings change (Service Display Name, Service UPN, and PSTN number). Keep the script session window open if you want to test settings. By doing so you don’t need to go through all steps again when you need to provision multiple teams.
Microsoft Graph PowerShell Permissions
Below is an overview of the steps performed by our provisioning script

An overview of our provisioning script
Provisioning – Step by Step
Get the provisioning script via direct link below. Pick the link depending on the chosen location:
INC Nimbus Provisioning Script URLs
🤔 What will this script do? Automate and guide you through the Azure-related setup on your Tenant. Refer to the detail steps below.
Script Details
🔍 Refer to the diagram above for an overview. During execution and depending on pending Service Settings changes the script will perform the steps below:

Pending changes on a Service will inform about a necessary Script-rerun
DONE?
💡 Please allow for a few minutes before making calls to a newly (re)configured Application Instance or PSTN number as it might take a moment for Microsoft Azure services to synchronize all the changes. 💡 Note that a rerun of this script is necessary for every additional Service and/or within your tenant.
Script Execution


Permission request dialog

Permission grant process
PSTN Licenses and Voice Policies
PSTN LicenseVoice Policy
The script allows you to choose how you would like to apply the required Phone System license to a service (Application Instance).The script will ask before any Online Voice Routing Policy should be applied to a service (Application Instance). 🔍 This is only required if your service is using a Direct Routing phone number. If you are using a phone number provided through Calling Plans or Operator Connect, you can skip the voice policy assignment.
💡 Via the same script functionality you can also remove Phone System licenses from Nimbus services.
💡 The script will only ask for an Online Voice Routing Policy assignment when a phone number is added or changed. If you wish to manually change the policy later on, you can do this via the Grant-CsOnlineVoiceRoutingPolicy command.
Script Conclusion and Rerun
When everything runs as expected you will see green DONE indicators and the script finishes.

Script conclusion and rerun dialog
💡 At the end you will be asked if you want to rerun the script:
Verifying changes via Test Call
Please allow for at least 5 minutes after applying script changes before making the call.
To test the call functionality:

Test call option in the service settings
💡 You can test this with 2 different Microsoft Teams client accounts in separate browser windows to simulate this call on your own as both caller and recipient.
💡 If you have assigned a PSTN license / phone number to the service it is also recommended to test calling it.
PSTN Limitations
Out of the box, Nimbus and related addons can only perform PSTN transfers according to Microsoft’s licensing and constraints.
Which PSTN license do I need to acquire?
As of 2023, “Microsoft Teams Phone Standard” licenses are no longer supported by Microsoft. Previously, those licenses were viable for Nimbus. Regardless if you are using Direct Routing, Calling Plans, Operator Connect, the “Microsoft Teams Phone Resource Account” license is now always required.
Your Setup
Required License
Direct Routing
“Microsoft Teams Phone Resource Account”
Calling Plan
“Microsoft Teams Phone Resource Account”+ “Microsoft Teams Domestic Calling Plan” or “Microsoft Teams Domestic and International Calling Plan” or “Microsoft Teams Calling Plan pay-as-you-go”+ “Communication Credits” (if these aren’t already included as part of your plan)
Operator Connect
“Microsoft Teams Phone Resource Account”
☝Please note that Luware staff cannot give recommendations on which license plan is best suited for your needs. Depending on your scenario, additional Teams App licenses may be required. Exact details are to be discussed with your Microsoft contacts.
How does PSTN licensing affect service and call transfers?
Scenario B – Service B is called directly instead. Now the workflow of Service B attempts a redirect to either service A or transfer to C. The PSTN transfer fails due to a missing license on Service B.

☝Note that handling and tracking of running cost for PSTN licenses is outside of the Luware support scope. If you require assistance in extending and/or configuring your Nimbus services for PSTN, our support will gladly assist you:
Luware Support Address
Issue / Error
Analysis/Workaround
“Script cannot be loaded because running scripts is disabled on this system.”
During Service Name Change: The script may encounter an error when trying to update the display name of a service.
Powershell fails to open popup window when authenticating to Nimbus.
Related Articles
Nimbus App Permissions



