-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sample "Proactive message bots app" missing AAD environment variabes when provision into azure env #1423
Comments
@ayachensiyuan - Thanks for reporting your issue. The bot-proactive-messaging-teamsfx sample provisioned and executed successfully. Could you please test this again and let me know if you face any issues here? |
@Nivedipa-MSFT thank for your reply. I still face this issue, the version of TTK is the same. It works in local debug. but when I run provision in to AZURE, it failed with that error. |
@ayachensiyuan - Could you please verify that all necessary environment variables are correctly set in your Azure portal? |
@Nivedipa-MSFT We have daily auto test for TTK, So this sample in TTK gallery failed since half month ago. Usually we test it according to readme file, It is certain that using the current version of TTK to create this sample and following the instructions in the readme to provision and deploy will encounter the problems mentioned above. All of this was automatically deployed by TTK, and I did not have to manually operate on Azure. Here's the test: https://github.com/OfficeDev/teams-toolkit/actions/runs/11419663804/job/31778539159 |
@ayachensiyuan - We have tested this on our end but were unable to reproduce the issue. Could you please clone the latest repository and test again? |
This PR fixed this sample issue, thanks. |
I use VSC teams toolkit to create sample "Proactive message bot" in sample gallery.
Sample: https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-proactive-messaging-teamsfx
When I provision in to azure, I have following issue.
The text was updated successfully, but these errors were encountered: