The Microsoft bot framework channel "Email" is not working. I tried to add different emails including Office 365, #outlook.com , #gmail.com, none of them working, The screen showing an error status "Unable to save email".
It seems this was working earlier. My email is accessible via email/password and office 365 enabled , but from bot framework email channel - its returning an error "Unable to save email". Could anyone please help on this.
Email channel can only be used with Office 365 accounts as described in the documentation here:
The Email channel currently works with Office 365 only. Other email
services are not currently supported.
So it will not work with #gmail.com accounts.
I checked again 2 minutes ago and from my side I also have the problem of getting Unable to save error during registration of the email (with an email that was previously working).
When having a look to the console of my navigator, I see that there is an internal server error (error 500) for POST https://dev.botframework.com/api/bots/myBotName/channels/email
=> I will log an issue on Github Bot framework's project
Related
Teams Application with a bot and the permission of the file uploading enabled.
Can't see the preview of the attachment sent to this bot on Microsoft Teams even if the JSON response of the file upload confirms the upload success.
The attachment is visible on the browser via the browser link (if we are logged in with the team's web app).
The error message is:
This item might not exist or is no longer available This item might
have been deleted, expired or you might not have permission to view
it. Contact the owner of this item for more information.
This issue got fixed though in this bug
I've created a bot based on the following sample:
https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/typescript_nodejs/57.teams-conversation-bot
Everything looks well so far and worked in my first bot. But with my second bot I've created when I start a conversation with the bot, I get a "Failed to send" error in Microsoft Teams on my desktop.
When I use teams in the web I can see in the dev tools the following error message for the request:
https://emea.ng.msg.teams.microsoft.com/v1/threads
Error:
One or more of the user ids provided are not valid.
I'm lost on what could be wrong. Any hint would be highly appreciated.
I was seeing the same error after creating a second bot for testing and realized I had forgotten to setup the Teams channel in Azure configuration.
So double-check that the Microsoft Teams channel is running:
I am trying to Post a Message from Post Man to Microsoft Teams can anyone please help me out with the steps. I download Microsoft Team in my personal Laptop and created Channel to which i want to send a message. Is it mandatory to create a BOT or we can use existing bots provided by Microsoft ?
I've integrated the Code from Microsoft.Bot.Sample.AadV2Bot in my own bot but the GetTokenDialog call always results in error "AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application: 'MYBOTSAPPID'"
As far as I understood, I do not have to register my bot in Azure Portal under "Azure Active Directory" but setup the Reply URL in the application registration Portal (https://apps.dev.microsoft.com) - Correct?
But whatever values I enter here, it won't work, neither locally via Emulator nor via Web. Furthermore, in MS Teams the signin Dialog does not work at all.
I've already tried these reply URLs without success:
https://MYBOTSNAME.azurewebsites.net, http://localhost:3978 and https://localhost:44362
I also tried to extend these with /api/messages, /signin-oidc and several other combinations, all without success.
The mentioned sample solution also does not include more keys than ConnectionName, MicrosoftAppId and MicrosoftAppPassword in web.config, so I haven't got a clue which redirect URI is taken on runtime.
In Azure Portal I've created an Azure Active Directory V2 Connection on my bot and entered my bot's Microsoft App ID in the field "Client ID" and Microsoft App Password in the field "Client Secret" - is this correct?
Any hint what I might have done wrong is VERY welcome!!
I finally could solve the Reply URL mismatch problem myself. Had to enter this Reply URL on my app in the application Registration Portal to make it work locally, via Emulator:
https://token.botframework.com/.auth/web/redirect
Still, the authentification Dialog (GetTokenDialog class from Microsoft.Bot.Builder.Dialogs) doesn't popup when I use MS Teams as channel.
Does anyone have an idea what could help?
I am new with the "outlook" api. i want to get all calender event,contact and mail from "outlook account".
but i does not get appropriate result with "outlook" account its working fine with "office365" account
i follow this documentation for get all required data
and i create application for getting data from here
but every time when i login with my outlook account it's give me an error like this.
Please help me out.
Thanks in advance...
Just ran into the same problem and found an explanation here. It appears we're going to have to wait for the accounts to be enabled unless you request a testing account as described in the link. Confirmed the same results when using the non-enabled account in the Outlook Oauth Sandbox.
From the first link
Because enabling mailboxes on Outlook.com for the Outlook REST API happens over a period of time, your existing Outlook.com account may take a while to get enabled. To test your app accessing data on Outlook.com mailboxes that have already been enabled, you can request a new, enabled Outlook.com developer preview account by emailing outlookdev#microsoft.com.
If your app accesses Outlook.com mailbox data, it should handle scenarios where the user's mailbox has not yet been enabled for the Outlook REST API. In such situations, when you make a REST request, you would get an error like the following:
HTTP error: 404
Error code: MailboxNotEnabledForRESTAPI or MailboxNotSupportedForRESTAPI
Error message: “REST API is not yet supported for this mailbox.
Step 1 :
Click the Below Link :
https://oauthplay.azurewebsites.net/?code=M657b8bab-e543-f849-134c-0a2f85179a67&state=17661047-2a14-4c90-9edd-0119f841b559
Step 2:
Step 3 :
Step 4 :
Step 5 :