I am trying to setup Windows (WNS) notifications based on following Microsoft tutorial: Send notifications to Universal Windows Platform apps using Azure Notification Hubs
System returns error at step 3 in chapter Configure WNS settings for the hub. Relevant screenshots below.
I used fresh Package SID created yesterday. Also, security key was properly created; as defined in tutorial.
Error message:
Error updating notification hub. Error. BadRequest. Message: **Invalid WNS credentials**.
App registration in Azure is visible under - Applications from personal account.
On Partner Center portal I have active individual developer account that was used to register application (MSIX or PWA app) and get Package SID.
Followed all steps in tutorial. Triple checked everything. No other errors received. Account that I used to go through the tutorial has OWNER permissions on Azure subscription where Notification Hub is located. Security and access rights shouldn't be the problem.
Any thoughts where is the problem? And where can I find more details about actual error?
screenshot-ErrorMessage
screenshot-App registration
screenshot-IntegrationAssistantSuggestions
Found solution.
Package SID should be in the format: ms-app://S-x-xx-x-xxxxxxxxxxxxxx....
And not in the format S-x-xx-x-xxxxxxxxxxxxxx.... (this is how it looks in partner center portal)
Resolved.
Related
I need to deploy a number of chatbots in Azure.
I made the botcode for the chatbots and tested them in the Bot Framework Emulator. Now I am ready to deploy them to Azure.
I haven't done this for a while. In the past, I used to create a resource called Web App Bot for this and deploy the botcode via Github.
This would give me a webapp bot resource and an app service that I could deploy my botcode to. Worked like a charm. This resource is not available anymore.
I did find a resource called Azure Bot. There is however no option to deploy any botcode to that resource.
I tried to create all resources via composer -> error and the request to file this in github
I tried to use Azure Cli -> error without any clear explanation.
Is it possible to just manually create all resources to host a Bot Framework chatbot on Azure and what are these steps?
Update 13 feb
I Created a Webapp for my botcode by just cloning a Webapp (from an earlier Web App Bot deployment) and changed the github repositiy. That works.
Next I created a Azure Bot. Changed the url to the url of the app and added api\messages to it.
Testing the bot results in:
Azure bot Webchat channel status overview:
"There was an error sending this message to your bot: HTTP status code InternalServerError"
Web App console:
"Error: Unauthorized. Invalid AppId passed on token"
So I added the Azure Bot's AppId (MicrosoftAppId) to the configuration of the WebApp.
Azure bot Webchat channel status overview:
"There was an error sending this message to your bot: HTTP status code InternalServerError"
Web App console:
"Failed to query knowledgebase: object Object UnhandledPromiseRejectionWarning: Error: BotFrameworkAdapter.processActivity(): 500 ERRORError: The clientSecret parameter is required" I guess I also need to add the MicrosoftAppPassword.
Press Manage Password in the configuration blade of the Azure bot -> Insufficient privileges to complete the operation.
Update 15 feb
6. I managed to create a new secret by visiting the Appregistration itself. Not being able to click Manager Passwords is a bug (I think)
I added to 2 application settings in the Web Appp. One for MicrosoftAppId and one for MicrosoftAppPassword (the secret). As value For the first setting I used Application (client) ID from the app registration
For the second I used the value of the secret I created in the app registration
Done. A working bot deployment
I have been using this MSDN tutorial (Tutorial: Send notifications to Universal Windows Platform apps using Azure Notification Hubs) to test the notification hub. The issue is it is asking me to create an app in Windows Store for which I need to register for Microsoft developer and it seems to be paid service. I'm trying to find an alternative here to get Package SID and Security Key for Windows (WNS) settings to register for an Azure Notification Hub. Please suggest.
The Windows Dev Center requires an account with a one time payment as specified on the Register to be an App Developer page.
I have used the Bot Builder Teams messaging extension sample and successfully debugged the project locally on my machine using ngrok. I then proceeded to follow the Azure deployment instructions, and successfully deployed my bot project to Azure.
However, I cannot find instructions regarding what values need to change within my project to now use the assets within Azure. I have enabled the Teams channel on the Bot Channel Registration resource that was provisioned, and I tried updating the botId value within my project's manifest file to match that of the newly provisioned app registration. But I'm still receiving an 'unable to reach app' message when sideloading the app in Teams.
Are there instructions regarding how/what to change within the project so it uses the Azure assets rather than my local ones?
To narrow down what's wrong, have you tried using the Web Chat to test the bot ? If this works, then the bot is working fine in Azure and the issue is for local teams to reach Azure.
Also verify that you are using the right AppID and Password.
Once you have verified that the bot is working in Azure, at the bottom of this page, you will see steps to get a url that you can paste to get the bot added in your local MS Teams instance. (quoting below for quick access)
Copy the https part of the code that is shown in the Get bot embed code dialog. For example,
https://teams.microsoft.com/l/chat/0/0?users=28:b8a22302e-9303-4e54-b348-343232.
In the browser, paste this address and then choose the Microsoft Teams app (client or web) that you use to add the bot to Teams. You
should be able to see the bot listed as a contact that you can send
messages to and receives messages from in Microsoft Teams.
I did finally get my bot working, but found several missing steps within the deployment documentation. I have reported them in a GitHub issue, associated with the relevant documentation article.
I am trying to release multiple projects in 1 solution using Azure Release pipeline
They are all connected to the same Azure Subscription, but some do deploy to the given app service while others give an unauthorized error.
Ive looked into it and i read that adding website_webdeploy_use_scm to the app service should help the Unauthorized error, but this didnt help for me.
What else could i look at? I connect through Azure Devops so i just selected the subscription from the list it automatically gathers from Azure because im logged in using the same logins as i use for Azure Portal
the full error is:
Connected to the remote computer ("xxxx.azurewebsites.windows.net") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Error: The remote server returned an error: (401) Unauthorized.
according to the error I'd suggest you check service principal permissions. it probably lacks the permissions required to manage those webapps.
So after refresh publishing profile in Azure Portal and trying it again it fixed itself so im not sure if that caused it or not but it worked!
another fix is to delete the slot and make it again
Given a VS web app project that has an existing Azure publish profile is there a way to tell what subscription the selected publish profile will publish the app to? We have such so many subscriptions it's quite time consuming to to use the portals poor blade interface to locate which subscription the app is in. Even opening the SCM site it seems apps know nothing about it's subscription.
As I know, we don't need Azure subscription information to publish our project. What we need is contentPath, ComputerName, UserName& Password when you use msdeploy. The following is the parameters that used to deploy:
.\msdeploy.exe -verb:sync -source:contentPath='E:\code' -dest:contentPath='sub2',ComputerName='https://waws-prod-sn1-047.ftp.azurewebsites.windows.net/msdeploy.axd?site=sub2',UserName='$sub2',Password='key',AuthType='Basic'
If we published project to Azure, we have no easy way to see which subscription it belongs to. I suggest you submit a voice at Azure feedback forum.