# June - 2024
It has been a couple of months since our last release, and our team has been working hard to bring the best of Ozone to our users, as you will see in the following release notes for June.
Our commitment to perfecting your Ozone experience grows as June unfolds. We've simplified workflows in recent versions by adding newer providers and enhancing our pipeline studio with an enriched user experience while creating pipelines and deployments, making it even simpler. While several minor fixes have gone into this release, below is a summary of what’s in store for this month. For context on the previous months, refer to our previous [release notes.](https://ozone.one/resources/release-notes)
### **New Features:**
**New Pipeline Studio:** This is one of the primary features our ozone team has worked on for the past few months. Now you can seamlessly work on creating pipelines and releases with just a drag and drop of pipeline and release templates. Not only that you can create workspace and parameters.
**Prisma Cloud provider as an integration:** We integrated Prisma Cloud with Ozone to enhance cloud security with threat detection, compliance monitoring, and vulnerability management. This will ensure secure access and protect containerized and serverless applications.
**Delete Feature:** "Delete Integrations (previously known as 'Providers') is now easier than ever in the latest release. Simply click the deletion option, confirm in the pop-up modal with a 'yes', and watch as your Integrations are seamlessly marked for removal."Not only do providers now you can delete schedules, and environments as well.
**Limited Agent feature:** Introducing the new Limited Agent feature in Ozone! Designed for clusters with secrets or secure deployments, this feature empowers users to connect their clusters to Ozone with confidence. Now, users can attach their clusters with specific namespaces and limited permissions, ensuring Ozone can perform CI/CD operations without accessing the entire cluster.
**AppDynamics Integration:** With these new integrations, Ozone empowers you to prioritize monitoring and application performance from the start, promoting performance optimization and a more resilient software delivery process.
We already support a new relic for application monitoring. In this release, we also added AppDynamics integration to help organizations ensure the optimal performance and availability of their applications.
### **Enhancements:**
**Enhanced Access and Permission Messaging:** To enhance user experience, we have implemented precise toaster messages across the Ozone platform. If users attempt to access features without the necessary permissions or access rights, they will now receive clear, specific messages. This ensures users understand that the feature is restricted due to plan settings or permissions.
**Support for Quay Triggers:** Users can now create webhooks for Quay Registry events, enabling automated responses to repository activities.
**Enhanced Backup Storage Visualization:** Improved visibility of backup storage location configuration for the MinIO provider within cluster environments, ensuring better clarity and ease of management.
**Studio Create Flow Integration:** Users are now seamlessly directed to the new studio after AI pipeline creation, whether initiated via prompt or external pipeline conversion.
**Cloud Storage Integrations for Data Backups:** Integrating cloud storage solutions like AWS S3, GCP Cloud Storage, and Azure Blob with Ozone to enhance data management by providing scalable, secure, and cost-effective storage options. These integrations facilitate seamless data backup and recovery, ensuring business continuity and minimizing data loss.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.ozone.one/ozone-end-user-guide/release-notes/june-2024.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.