Hi Ladan,

As the client secret is sensitive data, we do not store this plain text in the DataMiner.xml file. Instead there is a file with encrypted values that is used for storing this type of data.
During start up the DMA will read out the value and check whether it matches a sensitive data placeholder.
If it does, the value will be decrypted from that safe storage.
If it does not, then we interpret this as a new value and save this in said safe storage.

In this case, something may be going wrong with encrypting the new value, thus leading to the previous value being read from the safe storage.

Would it be possible to try the following steps?

1. Stop the DataMiner Agent, you can verify that everything is properly stopped by checking the processes in the task manager. Only SLWatchdog should still be running out of all the SL* processes.
   Note: If it is part of a failover pair, both agents need to be stopped and all subsequent steps applied to both agents.
2. Using the file explorer browse to and open “C:\Skyline DataMiner\Files\SyncInfo\{DO_NOT_REMOVE_32D5A837-E15E-4104-A37F-CBF6ED139620}.xml”. Within this file remove the <Encryption> entries with the following key: {5C104E97-5455-4527-A7EE-C01EBA036496} and save the file.
   This will remove the encrypted value that is stored for the client secret.
3. Now browse to and open “C:\Skyline DataMiner\DataMiner.xml” here you can apply the configuration for your PreProd Azure as you’ve done before and save the file.
4. Restart the DataMiner Agent, restart its buddy as well in case it is part of a failover pair.

Please do let me know if the above has worked for you, if not then we can open a ticket to investigate this more in depth and arrange a session to resolve this.