Finance | Project Operations, Human Resources, ...

Connecting to UAT environment from DevTest Environment and KeyVault Secrets

(1) Share

Report

Posted on by Community member

Hello, I have been working on debugging a UAT environment through a DevTest environment and had some issues with encryption. I have checked through this post here:
Encryption error while debugging UAT environment from Devtest environment (dynamics.com)

I see that importing in secrets between environments isn't possible since that's a Microsoft limitation currently. In this case however, since the Devtest environment is connecting to the UAT database rather than importing the data, I would have thought the secrets could carry over in this way. Correct me if I am wrong, but is there still a way to get around the issue of having to re-enter in secrets when connecting through Devtest? Thanks in advance.

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

PerezAguiar Microsoft Employee on at

Like (1)

Report

hey!

The link you've shared seems broken. However, and as a general Security behavior: If environment 1 is encrypted with some credentials/key, any kind of access to this data either from another environment or from a tool that will simply connect, will require to decrypt such data with the right key. Other environments most likely will NOT be encrypted the same way or with same key. Therefore, you should use the appropriate credentials/Key to access the data on it.

This is valid to connect/read the data from that environment. Even if it's another environment on the same tenant, the condition should still apply: Connection will require the appropriate key/Credentials.

Regards,

Was this reply helpful? Yes No
Community member 4 on at

Like (0)

Report

I can't access your link. What's wrong with it?

https://learn.microsoft.com/en-us/geometry dash online /powershell/module/microsoft.crm.powershell/?view=dynamics365ce-ps

Was this reply helpful? Yes No
Community member 8 on at

Like (0)

Report

Hello,

the link should be updated properly now, not sure why it wasn't working before.
Thanks for the response, that clears up a lot for me. Currently both environments should be using the same keys from the same keyvault. When you say connection will require the appropriate credentials, shouldn't this follow those conditions then? Or is the encryption still going to be different?

Was this reply helpful? Yes No
Suggested answer

Anton Venter 20,345 Super User 2025 Season 2 on at

Like (2)

Report

The Key vault secret to access the Key vault in F&O, is encrypted and stored in the database. The key used to encrypt/decrypt this data is on the environment/AOS. Each environment/AOS has its own key. The problem is, you are accessing the UAT data from the Dev environment which is probably using the Dev key to decrypt the Key vault secret.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Connecting to UAT environment from DevTest Environment and KeyVault Secrets

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Connecting to UAT environment from DevTest Environment and KeyVault Secrets

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates