Time flies when you're shipping code! It feels like we were just celebrating the New Year, reflecting on the past year, and now Valentine’s Day is already around the corner. This week, we tackled features that enterprise customers have been asking for, starting with Single Sign-On, alongside other improvements we’re excited to share with you!
If you’ve got feedback or feature requests, you can book time with us to chat, or find us in our Slack community, LinkedIn, X, and BlueSky.
Spotlights
Microsoft Entra ID Single Sign-On
At Tempest, security is a top priority. We’re introducing support for Single Sign-On to help large-scale organizations securely manage access to their Tempest organization. We're starting with Microsoft Entra ID, a leading identity provider, and plan to integrate additional providers in future releases. You can configure SSO under your Organization settings.
See more details in our documentation.

We also gave our login screen a new look! If your organization has enabled Single Sign-On, users can enter their email address to be redirected to their identity provider's page to complete sign-in.

Improvements & Bug Fixes
Security
As mentioned earlier, we take security seriously. We've added GraphQL Armor to strengthen our protection against common GraphQL vulnerabilities.
Developer ecosystem
The Tempest CLI now allows you to configure how long it waits for app execution.
Recipes, projects, deployments
Text search is now case-insensitive throughout the product.
We fixed a bug in column sorting.
We've made the sorting experience consistent across all tables.
Private App enhancements
It is now possible to load schemas from multiple App versions.

We fixed a bug where deleted Private Apps were still showing up in lists.
We fixed a bug where right-clicking on a Private App resource and picking "View in Playground" wouldn't load the correct schema.
We added an explicit (and discoverable) button for launching the Playground directly from a Private App version page.
