Notification blob storage is not filled

[Aaron0176]

Question based on #355.

I'm facing the issue that my bot installations are not recognized when I deploy my app to Azure.

That's why I try to introduce a blob storage as described here.

My container is created successfully and I don't see error, but container stays empty and no bot installations seem to be persisted.

Any ideas?

[jamesburton85]

Im having the same issue, did you manage to resolve this?

[Aaron0176]

Hi James, for me it was related to the single tenancy setting of my AAD app...

Find the detailed discussion here:
MicrosoftDocs/msteams-docs#7920

[swatDong]

The initial issue was solved per MicrosoftDocs/msteams-docs#7920
To use single tenancy bot, make sure @microsoft/teamsfx SDK is upgraded to ^2.2.0 and set correct MicrosoftAppType and MicrosoftAppTenantId.

[swatDong]

@jamesburton85 - do you still have the issue? Would you mind share more details or file another issue to track?

[muiruri]

I am facing this issue, it has been 2 days of trying and nothing seems to work.
I have a Teams SSO Tab app, I added the Notification Bot feature and everything works okay when running locally. After provisioning and deploying to Azure, the notification bot isn't working. I added Storage and noticed that the installation is not being recorded. I have timerTrigger which executes but finds no installations. The storage container is empty.

I created a totally new Teams SSO Tab app and added the notification bot feature. This also did not work either. The Storage container is created but not installation is recorded.

I created a Standalone Notification Bot and this worked okay without any issue.

I added SSO enabled Tab feature to the Bot application and after provisioning, deploying and running, the installation is not being recorded. I had uninstalled the Bot and the installation was removed from the container.

Is there any special case with SSO Tab + Notification Bot when they are together?

[swatDong]

@muiruri - Since your app works well on local, there may be some mis-configuration on your Azure resources. Is it convenient for you to share your .bicep files? Feel free to remove any personal info such as resource name or app settings.

[muiruri]

@swatDong They are all the auto generated files, I only edited the botService.bicep to add the msaAppType value of MultiTenant

The bicep files from ./templates/azure/provision

botService.bicep : https://pastebin.com/04uxQdBS
azureFunctionBot.bicep : https://pastebin.com/C9btGD55
identity.bicep : https://pastebin.com/a8jgQ7s5
frontendHosting.bicep : https://pastebin.com/7yD9DbGj

[swatDong]

@muiruri Your bicep files from ./templates/azure/provision look good.

I tried on my side and can also repro your issue. The cause I found is that "Authentication is enabled on the Azure Functions". It seems the templates/azure/teamsFx/azureFunctionBotConfig.bicep has unexpected auth settings (diff from the pure notification project).

A quick workaround is - disable the auth in templates/azure/teamsFx/azureFunctionBotConfig.bicep and provision again.

Also verify the status from Azure Portal:

After that, you can message your bot (or uninstall / reinstall) to see if installation is added to your storage container.

@hund030 - FYI since it's related to azure function bicep. I'll log a bug to track internally.

[muiruri]

@swatDong Thanks for your help. It is now working.