Message ID: MC911638
We are announcing the ability to use your own encryption key for encrypting data at-rest for existing environments with flows in Power Automate. This will enable you to meet your data and privacy policy guidelines. This feature will reach general availability on November 15, 2024.
How does this affect me?
You will be able to use your own encryption key from your Azure Key Vault to encrypt an environment that already has running Power Automate flows. Previously, only environments without prior Power Automate usage were supported for customer-managed encryption keys.
What do I need to do to prepare?
This message is for awareness. No action is required.
Source: Microsoft
Hey there, fellow tech enthusiasts!
Have you heard the buzz about the latest update in Power Automate? The ability to use your own encryption key for protecting data at-rest for existing environments with flows is truly a game-changer! ️
For admins, this update means more control over data security and better compliance with privacy policies. Being able to use your own encryption key from Azure Key Vault for environments with running Power Automate flows is a big step towards ensuring data protection. Plus, it simplifies the process and gives peace of mind knowing your data is secure. ️
As for users, this update might not directly impact your day-to-day flow (pun intended ), but it’s reassuring to know that the platform is continuously improving its security measures to keep your data safe. It’s a win-win for everyone involved!
So, how impactful are these changes? Well, they might not cause fireworks or confetti to rain down from the sky, but they are definitely significant in enhancing data security and privacy compliance. It’s the little things like this that make a big difference in the long run!
I’d love to hear your thoughts on this update! Do you think it will make a noticeable difference in how you use Power Automate? Share your comments below and let’s keep the conversation going! ✨