[CoE Starter Kit - QUESTION] Updating Secret Value for Command Centre and Audit Logs

[G1982C]

Does this question already exist in our backlog?

• I have checked and confirm this is a new question.

What is your question?

Hi,

The secret value for the app registration for the Command Centre and Audit Logs has expired. I now have a new Secret ID and Value for the existing Application (client) ID, although I wanted to check what I need to update in the CoE. Sorry to trouble you but I couldn't find anything online on how to specifically do this and don't want to get it wrong.

I need to update this for both the cloud flows and the BYODL Data Export CoE. i believe from memorry the BYODL doesn't need the audit log app anymore as it manages it differently.

Could you please share a link or some guidance on what I exactly need to update for both?

Thanks

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.8 and 4.42

What app or flow are you having the issue with?

No response

What method are you using to get inventory and telemetry?

None

[Jenefer-Monroe]

Sorry I'm having a little trouble following. Let's handle these one at a time as a result.

First it sounds like the secret for this app registration has expired. Is that accurate?
If so, you just need to update the secret. If you are storing as plain text you can do that right there in he Command Center app, if not, and you are storing in Azure Key Vault, then you need to update the secret using the product UX itself.
Use Azure Key Vault secrets

[G1982C]

Correct, the app registration has expired and I have a new secret. We are storing it as plain text.

I have just used the Command Center to update the secret for the Cloud Flows CoE Solution. Although I have just opened up the Command Center for the Data Flows CoE solution that I have in test and there is no environment variable section? Do I need to update this somewhere else?

[Jenefer-Monroe]

Oh thats the CoE Maker Command Center, you need the CoE Admin Command Center. :

[G1982C]

Doh, thank you. Interestingly the Client ID and Secret were blank in the BYODL Admin Command Center, so I have added those in.

Is the only other change I need to make to add the new secret to the Office 365 Management API connection? As below

Thanks

[Jenefer-Monroe]

If you are using the BYODL architecture then you dont need the audit log solution, those are native in the datalake from the product itself. Let's check that. Please browse Admin Command Center > Environment Variables > What is the value for this item?

[Jenefer-Monroe]

I tested around and it looks like the documentation tells you that you need these permissions to use the secrets as an env var.
Where both the user and the Dataverse object are Key Vault Secret Users

But from my testing what you actually need is this:
Where the user running the flow is both Key Vault Secret User and Key Vault Contributor

[G1982C]

Sorry for the late reply. For the BYODL solution this is the environment variable value that you requested above. Thanks

[Jenefer-Monroe]

ok you should not turn on the audit logs then if you are using the BYODL, it brings in app usage natively.

[G1982C]

Thanks Jenefer. For the cloud flows \ dataverse CoE solution, I noticed that the audit logs using the custom connector is being deprecated and replaced by a HTTP connector as part of the core solution. I have transitioned over to the new flows.

Although just a quick question, is the BYODL data flow CoE solution still in preview or are we ok to move this into production and no longer use the Cloud Flows \ Dataverse CoE solution?