'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Microsoft Places Deployment and Subscription Requirements Guide
Question details
Administrators need guidance on handling unexpected subscription selections during Microsoft Places deployment and determining the best environment for testing preview features.
- Product
- Microsoft Places
- Device & OS
- not provided
- Scenario
- Running the Microsoft Places preparation script for deployment and planning to test advanced public preview features.
- Observed behavior
- The preparation script selects an unexpected tenant or subscription (like BAT-DEV), and administrators are unsure if this should be changed or where preview features should be safely tested.
Ensure you have the necessary administrative privileges and the latest PowerShell modules installed before modifying tenant or subscription configurations for Microsoft Places.
Manage Subscription Selection and Preview Testing
Guidelines for handling the preparation script's subscription choice and safely testing Microsoft Places features without impacting production.
During deployment, the preparation script automatically selects an available subscription. In most cases, this default selection is sufficient for the deployment to proceed smoothly.
There is no general requirement to change the auto-selected subscription (such as BAT-DEV) unless a different subscription is strictly necessary for the specific users and resources you are enabling.
To avoid affecting your production environment, always test Microsoft Places advanced features that are in public preview within a completely separate test tenant.
Ensure that the licensing and subscription configuration you ultimately proceed with corresponds directly to the users and resources being enabled in Microsoft Places.
If you encounter script-specific errors or PowerShell deployment issues during the setup, consult the Microsoft PowerShell community forums for specialized troubleshooting.
Looking for a simpler, lightweight Office suite?
If managing complex Microsoft 365 enterprise deployments, tenant scripts, and subscription requirements is overwhelming for your basic document needs, WPS Office offers a powerful, lightweight, and hassle-free alternative.
- 1. Download the installer: Visit the official WPS Office website and click the Free Download button.
- 2. Install the software: Run the downloaded installer file and follow the straightforward on-screen instructions.
- 3. Start creating: Open WPS Office to instantly create, edit, and save your documents, spreadsheets, and presentations.
Frequently Asked Questions
Can I test Microsoft Places preview features in my production tenant?
While technically possible, it is highly recommended to test public preview features in a separate test tenant. This prevents experimental features from causing unintended disruptions or configuration issues in your live production environment.
Why did the preparation script select the BAT-DEV subscription?
The script auto-selects available subscriptions based on your tenant's current licensing state. You do not need to change this default selection unless a different subscription is explicitly required for the specific resources you are deploying.
Where can I get help for PowerShell errors during the Microsoft Places deployment?
Because the deployment relies heavily on PowerShell scripts, the most effective place to troubleshoot script-specific errors and execution policies is the official Microsoft PowerShell community or Microsoft Q&A forums.
