Issues in using Company Communicator App after Deployment

[roset0130]

Hi Team,

Asking for your inputs on the error below after us deploying the Company Communicator application on Teams. We are able see the application on Teams but when we try to create/compose a message we are receiving this error. Appreciate your insights/help on this issue.

[gsv022]

Hi @roset0130 ,
Can you check if the client secret you provided in your app service and/or Key Vault is the same as what you got from your app registration?
From the error message, the secret provided may be 1) incorrect or 2) expired

[roset0130]

Hi,

The client secret was newly generated when we deployed the applications using the Azure admin center. We also did not receive the error in deploying the application. But to be safe, how can we check the secret key on the app? We did not use the powershell deployment for your reference.

[gsv022]

@roset0130 , below are the steps to check if the client secret is expired or not, if expired provided the steps how to create newly and update it, please let me know if you've any follow up questions.

• To find author bot app id, go to Azure portal -> look for Company Communicator App services -> Configuration -> Author AppId

• Click show values and copy the Id.

• Go to App Registration and search for the app with id you copied above.

• Go the author app registration -> Certificates & secrets -> Check for expiry date of the secret

If the secret is already expired, click ‘New client secret’ and generate it

• Copy the value, navigate to the Azure key vault for Company Communicator -> Secrets -> update the AuthorAppPassword

• Restart the app services, function apps

[roset0130]

The Secret key is not expired, but when I go to Key Vault to check the ID, it says "List" is not enabled and I am not authorised to view the contents.

I'm clearly the Owner:

And I've allowed "List" under Access Policies:

Please check on what are the other options that we need to take to use the Company Communicator

[gsv022]

As you mentioned that app secrets were not expired. Could you please compare the client secret of each app registration in keyvaults. To check that

Goto resource group-->Keyvaults-->Access policies-->Add Access Policy-->Configure from Template-->Select Key, secret,Certificate Management-->Go for Select principal-->Enter your id-->Click add-->Now goto secrets-->Open particular app registration-->Click show secret value-->Compare

[gsv022]

Hi @roset0130 ,

Did the above steps work and solved the issue? Please let us know.

Thank you.

[oed-mueckek]

Hello, maybe we have a problem with the secrets as well as the sign in log for the Communicator App says:

I already changed the secret for the author app to a new one and restarted the app service and function apps, but no luck :(

any ideas?

[gsv022]

Hi @roset0130 ,

• Please do make sure that the secret value is being copied instead of secret ID.

• The copied secret value in author app should be pasted in configuration of app service. The same has to be done for prep-function and data function as well.

• Re-sync the app service and function apps again.

[gsv022]

Hi @roset0130 ,
Could you please let us know the status whether above steps helped or not.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.