If this material is helpful, please leave a comment and support us to continue.
Table of Contents
When discussing the deployment of new features and services in Microsoft 365, it is important to understand the three key release phases: Private Preview, Public Preview, and General Availability (GA). Each phase represents a different stage in the development and release process, with varying levels of access, support, stability, and completeness.
The Private Preview phase is the initial testing and development phase where a limited number of participants are given access to a new feature or service. This is often by invitation only and is used to gather feedback from a select group of users who test the functionality in a controlled environment. The participants are usually under a Non-Disclosure Agreement (NDA) and are expected to provide detailed feedback and report issues.
For example, a new security feature in Microsoft 365 might be released to a small group of large enterprise customers to gather initial feedback before making it more widely available.
Following the Private Preview, the Public Preview phase opens the testing to a broader audience. While still not the final version, the service or feature is now sufficiently stable for use in non-production environments or for testing in production with the understanding that it’s not fully supported. Public Preview is a critical step in the development process because it allows Microsoft to collect feedback from a wide range of users and environments, thus identifying any additional issues before the full release.
An example of a Public Preview might be the introduction of a new collaboration tool within Microsoft Teams, where any Microsoft 365 customer can enable and try out the new feature and provide feedback, but with the understanding that there may still be bugs, and the feature set may not be complete.
In the world of cloud computing services like Microsoft Azure, General Availability (GA) is a critical stage in the release process of a product or service. GA indicates that the service or product has completed its preview phases, including private and public previews, and is now ready for production use with all the applicable warranties and support from Microsoft.
General Availability means the Azure service or feature is deemed fully developed, stable, and operational for enterprise use. It has been tested across multiple scenarios and validated for performance, security, and compatibility. It also implies that the service is now backed by Azure’s service level agreements (SLAs), providing customers with guarantees about the availability and performance of the service.
Once a service reaches GA, it is available to all Azure customers, and they can implement it into their production environments with confidence.
Before reaching General Availability, an Azure service will typically go through the following stages:
Release Stage | Description | SLA | Pricing | Support |
---|---|---|---|---|
Private Preview | Limited to certain users for initial feedback | None | Not Applicable | Limited |
Public Preview | Open for all users to test with the possibility of no charge | None | Reduced or Free | Limited |
General Availability | Fully supported release ready for production use | Full | Standard | Full Support |
General Availability carries significant implications for Azure customers:
Microsoft announces GA through various channels, such as:
General Availability is a milestone in the lifecycle of Azure services, indicating they are ready for widespread use in production environments. It means that Microsoft fully supports the service with a service level agreement, and it meets the company’s standards for security, reliability, and compliance. Customers wanting to implement new Azure services in their infrastructure should look for GA announcements to ensure they are making decisions based on services that are fully developed and supported. With GA, Azure continues to expand its robust cloud platform with a growing suite of services tailor-made for enterprise use-cases.
As an example, a new compliance feature that has passed through Private and Public Previews will be rolled out in GA, which means it is now officially part of the Microsoft 365 suite with full functionality, documentation, and support available.
Phase | Accessibility | Purpose | Support Level | Stability |
---|---|---|---|---|
Private Preview | Invite-only | Early feedback collection and issue identification | Limited support | Least stable |
Public Preview | Open to all | Broader testing, feedback collection, and issue resolution | Partial support | More stable than Private Preview |
General Availability (GA) | Available to all subscribers | Full production use with complete feature set and full support | Full Microsoft support | Fully stable |
In conclusion, Private Preview, Public Preview, and General Availability are three distinct phases in the release of new Microsoft 365 features or services. Each stage serves a specific purpose and provides different levels of stability and support. By understanding these phases, businesses and IT professionals can better plan their adoption strategies for new Microsoft 365 updates, ensuring they leverage the latest innovations with the appropriate balance between early access and stability.
False
The General Availability (GA) phase is the last phase where the product or service is released to all customers, following the Public Preview.
Private Preview
In the Private Preview phase, only a selected group of customers have access to the feature for testing purposes.
True
General Availability indicates that the product or service is stable, fully supported, and ready for production use.
End of Service
After a product reaches General Availability, it eventually enters the End of Service phase when support ends and it may be replaced by newer offerings.
True
Features in Public Preview are generally not fully supported, as they are still being tested and feedback is being gathered.
Public Preview
Public Preview allows all customers to test and give feedback on features, but it comes with a disclaimer that changes could occur before GA.
False
During Private Preview, a product might still be in development. Features could be added or refined based on feedback before it becomes feature-complete at GA.
GA features are fully supported and have SLA guarantees.
General Availability features are production-ready, fully supported, and come with SLA guarantees.
False
Only a selected group of customers participate in Private Preview, thus only they can provide direct feedback during this phase.
It’s automatically available to them
Features in Public Preview are typically made available to all users, and they can choose to test them without needing special access or agreements.
False
Features may still receive updates and improvements post-GA; however, these usually focus on enhancements or bug fixes rather than core changes to functionality.
General Availability
During the General Availability phase, the feature or service is expected to be at its highest level of stability and reliability for all customers.
Private preview is a phase in the lifecycle of Microsoft 365 services where a limited group of customers is given early access to test new features and provide feedback.
Customers who participate in private preview programs get to test new features before they are generally available, and provide feedback that can influence the development of the feature. They also get to use the new feature in a controlled environment and make sure it meets their specific needs.
Public preview is a phase in the lifecycle of Microsoft 365 services where a wider audience is given access to test new features and provide feedback.
Customers who participate in public preview programs get to test new features before they are generally available, and provide feedback that can influence the development of the feature. They also get to use the new feature in a wider, more realistic environment.
General availability (GA) is the final stage in the lifecycle of Microsoft 365 services, where a feature or service is released for public use.
Microsoft evaluates feedback from customers in the private and public preview phases, as well as other factors such as performance, stability, and security, to determine when a service or feature is ready for general availability.
Private preview is a limited, controlled testing environment for a small group of customers, while public preview is a wider testing environment for a larger group of customers.
Having multiple phases in the lifecycle of a Microsoft 365 service allows for a more controlled and iterative approach to developing and releasing new features. It also allows for customer feedback to be incorporated into the development process.
Customers can usually sign up to participate in a private or public preview program through the Microsoft 365 admin center or other relevant portals. Microsoft may also reach out to specific customers directly to invite them to participate.
Features in preview may not be fully tested or stable, and may have bugs or other issues that could impact the user experience. Additionally, features in preview may not be fully documented, which could lead to confusion or incorrect usage.
If a feature in preview doesn’t receive enough positive feedback, Microsoft may choose to delay or cancel the release of the feature.
Yes, customers can continue to provide feedback on Microsoft 365 services and features even after they have been released for general availability.
Microsoft collects and evaluates customer feedback through various channels, such as surveys, forums, and support tickets. They use this feedback to prioritize feature requests and make improvements to existing features.
A phased approach to feature releases allows Microsoft to gather feedback from customers in a controlled environment before releasing a feature to a wider audience. This can help ensure that features are well-designed and meet the needs of customers.
Yes, customers can usually opt out of a public preview program
34 Replies to “Describe private, public preview, and general availability (GA) options”
As an IT admin, how can I provide feedback for features in private preview?
Most private previews include a direct line of communication to the product team, often via a feedback form or an assigned account manager.
Can features be removed after they’ve been moved to GA due to unforeseen issues?
It’s rare, but it can happen. Usually, Microsoft will provide a deprecation timeline to give users ample notice.
Could someone explain why features sometimes remain in public preview for a long time before going GA?
It often depends on the complexity of the feature and the amount of feedback the development team needs to make it stable.
This has been a useful discussion, thanks everyone!
Appreciate the clear distinction between these stages in your discussion!
I found some features in public preview relatively stable, but still a bit risky for daily use.
Absolutely, and that’s why it’s always good to test the features in a non-production environment before full deployment.
Can anyone explain the difference between private preview and public preview in Microsoft 365 services?
Sure! Private preview is typically available to a select group of customers and requires an invitation. Public preview, on the other hand, is available to all customers who want to try the new feature.
Where can I find the list of features currently in public preview for Microsoft 365?
You can check the Microsoft 365 roadmap or the official Microsoft documentation page for that information.
Thanks for the breakdown on this topic, quite informative.
This post was a great help, thanks!
How does general availability (GA) differ from the preview stages?
GA is the stage where the feature is fully tested and considered stable, available to all users without restrictions.
Is it safe to use features in public preview for critical business operations?
I would advise against it as public preview features are still in testing and can have bugs or be changed before GA.
Why is private preview not accessible to everyone?
Private previews are usually limited to manage the feedback and ensure that the initial group can provide detailed insights before a broader rollout.
What are the risks associated with using a feature in private preview?
The main risks are potential bugs and incomplete functionality, as the feature is still under development and may change significantly before GA.
I’m interested in joining the private preview program for Microsoft Teams.
You’d need to reach out to your Microsoft account manager or check if there’s a sign-up page available for that specific program.
When does Microsoft usually move a service from public preview to GA?
This varies but generally after getting enough user feedback and ensuring the service is stable and meets all quality standards.
The difference between private and public preview stages makes much more sense to me now, thanks for explaining!
Is there a cost difference between using a service in preview vs in GA?
Typically, preview services are available at no extra cost because they are still in the testing phase. However, billing policies can vary.
Sorry, but I think this post could have been more detailed about how to enroll in private previews.
Is there a sandbox environment to test public preview features?
Yes, Microsoft 365 often provides sandbox environments specifically for testing features that are in preview.