[CoE Starter Kit - BUG] ISSUE TITLE. Admin | Audit Logs | Sync Audit Logs (V2)

[winco7]

Does this bug already exist in our backlog?

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

Describe the issue

November 2024 version COE

Allways fail Audit Logs | Sync Audit Logs (V2).

Error occured while reading secret: Value cannot be null.
Parameter name: input

{
"host": {
"connectionReferenceName": "shared_commondataserviceforapps_1",
"operationId": "PerformUnboundAction"
},
"parameters": {
"actionName": "RetrieveEnvironmentVariableSecretValue",
"item/EnvironmentVariableName": "admin_auditlogsclientazuresecret"
}
}

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

3.25

What app or flow are you having the issue with?

Admin | Audit Logs | Sync Audit Logs (V2)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Can you please validate the following

1. Which api are you using for the audit log?

• Graph API
• Office 365 Management API

2. Are you storing your app registration in Azure Key Vault? Or as plain text.

[winco7]

Hi. 1. Which api are you using for the audit log? * Graph API<https://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http-graphapi> * Office 365 Management API<https://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http> 1. Are you storing your app registration in Azure Key Vault? Or as plain text. --> plain text Un saludo. [logoenagas]DSI.GOSC.WIN.CO (INDRA) – FRANCISCO J.VIDAL SANCHO Gerencia de Operaciones de Sistemas y Comunicaciones Dirección de Digitalización, IA e Innovación Tel.: + 34 917 099 718 ***@***.******@***.***/> / ***@***.******@***.***> Enagás, S.A. Titan, 8 - 28045 Madrid [lineahorizontal] De: Jenefer Monroe ***@***.***> Enviado el: martes, 17 de diciembre de 2024 14:05 Para: microsoft/coe-starter-kit ***@***.***> CC: DSI.GOSC.WIN.CO ***@***.***>; Author ***@***.***> Asunto: Re: [microsoft/coe-starter-kit] [CoE Starter Kit - BUG] ISSUE TITLE. Admin | Audit Logs | Sync Audit Logs (V2) (Issue #9417) Advertencia de Seguridad Este correo es externo a Enagás. Verifica el remitente y no abras archivos adjuntos ni hagas clic en enlaces si no tienes la seguridad de que son legítimos. En caso de duda, contacta con el CAU.

…

________________________________ Can you please validate the following 1. Which api are you using for the audit log? * Graph API<https://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http-graphapi> * Office 365 Management API<https://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http> 1. Are you storing your app registration in Azure Key Vault? Or as plain text. — Reply to this email directly, view it on GitHub<#9417 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNVBNYZVK64P77UATN27RY32GAOPPAVCNFSM6AAAAABTX6MO2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGQYDSOJUGU>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[Durk1969]

@Jenefer-Monroe same problem here. The problem has been going on for a while. The error message is: Action Get_Azure_Secret has failed.

We use the following API:

[Jenefer-Monroe]

Hi. 1. Which api are you using for the audit log? * Graph APIhttps://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http-graphapi * Office 365 Management APIhttps://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http 1. Are you storing your app registration in Azure Key Vault? Or as plain text. --> plain text Un saludo. [logoenagas]DSI.GOSC.WIN.CO (INDRA) – FRANCISCO J.VIDAL SANCHO Gerencia de Operaciones de Sistemas y Comunicaciones Dirección de Digitalización, IA e Innovación Tel.: + 34 917 099 718 @.@./> / @.@.> Enagás, S.A. Titan, 8 - 28045 Madrid [lineahorizontal] De: Jenefer Monroe @.> Enviado el: martes, 17 de diciembre de 2024 14:05 Para: microsoft/coe-starter-kit @.> CC: DSI.GOSC.WIN.CO @.>; Author @.> Asunto: Re: [microsoft/coe-starter-kit] [CoE Starter Kit - BUG] ISSUE TITLE. Admin | Audit Logs | Sync Audit Logs (V2) (Issue #9417) Advertencia de Seguridad Este correo es externo a Enagás. Verifica el remitente y no abras archivos adjuntos ni hagas clic en enlaces si no tienes la seguridad de que son legítimos. En caso de duda, contacta con el CAU.
…
________________________________ Can you please validate the following 1. Which api are you using for the audit log? * Graph APIhttps://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http-graphapi * Office 365 Management APIhttps://learn.microsoft.com/power-platform/guidance/coe/setup-auditlog-http 1. Are you storing your app registration in Azure Key Vault? Or as plain text. — Reply to this email directly, view it on GitHub<#9417 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BNVBNYZVK64P77UATN27RY32GAOPPAVCNFSM6AAAAABTX6MO2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGQYDSOJUGU. You are receiving this because you authored the thread.Message ID: @.@.>>

Its difficult to see your response, I think you told me you are using plain text but you did not tell me which API you are using.

[Jenefer-Monroe]

For both of you, note that if you are using plain text to store the secret then this failure is expected and caught. You need to find the failure lower down in the flow.

@Durk1969 you should probably post a new issue as typically these are configuration issues and so we will want to walk through your configuration separately.

Below is more information on how to find the terminating failure.

Find terminating failure

Please note that failures like this are caught/expected failures.
We use these calls to see if the object is new to the inventory, and if it is, this call to “get it” will fail. This failure is caught and the “isnew” variable is set to true.

In order to debug you need to find the terminating failure in the flow. Here for example the call to “forced failure” failed, and was not caught, so the flow terminated here. That is the spot you need to find in your failure in order to debug.

[Durk1969]

Hi @Jenefer-Monroe, due to the holidays my respons is a bit later.

In the example you mentioned above I see Admin | Sync Template v3 (Flows). We don't have this flow (anymore).
The sync Flow that fails with us is: Admin | Audit Logs | Sync Audit Logs (V2).

In answer to your previous question which API you are using I think we are using Office 365 Management API Azure AD service principal.

If it is necessary to post a new issue I will do that.

[Jenefer-Monroe]

Yes please do post another issue. And add that detail about the API you are using.

[Durk1969]

Hi @Jenefer-Monroe , i made e new issue: #9487.

[Jenefer-Monroe]

Wonderful, I no longer own triaging new issues but someone else should be along to assist you shortly.

I'm closing this issue out due to OP responses ceasing so no more action for starter kit team.