[CW-1400] Getting Microsoft Email working with Chatwoot in 2023 #6729
Comments
|
@evolve2k Thanks for the detailed note.
Is it a consistent behaviour? We have customers using Chatwoot with Microsoft Email in production, haven't heard a complaint recently. Anyway, happy to help with the implementation if required. |
pranavrajs
added
the
feature-request
|
I would guess that they setup in 2022 before this came into affect, it probably only affects new people setting up in 2023. If they registered this year, they likley registered a multi-tenancy access app had to get their organisation verified, which is a more involved process and requires providing legal documentation, accepting a bunch of additional terms and manual approvals on Microsofts end. It's much much better if we can avoid verification. This PR means for single tenancy access organisational verification is avoided and Microsofts new required approach for single tenacy access is supported. The reference PR is working and we're using it internally. |
sojan-official
changed the title
sojan-official
added
the
investigation
|
Checking in on this one. |
sojan-official
modified the milestones:
🧉 April 11 - April 17,
🧞♂️ April 18 - April 25,
🧛♂️ April 11 - April 19
sojan-official
modified the milestones:
🧛♂️ April 11 - April 19,
🪴 May 2 - May 8,
🚄 May 9 - May 15
|
sojan-official
assigned tejaswinichile and sojan-official and unassigned tejaswinichile and sojan-official
|
Hi @sojan-official , @tejaswinichile any update about this issue? Thanks |
|
Hey Folks, What's the status of this issue? Is it available for early tests anywhere? |
|
I just looked at #6878 and it was all merged 11 April 2023. So this should all be in place and working now as far as I can tell. If you are having a similar issue, I’d suggest to raise a new Issue. |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
As of 2023 basic auth is totally removed (following Microsofts deprecation notices in 2022).
Getting Microsoft Email has become complicated in 2023 and Microsoft arent helping things.
This issue is to address a range of issues that are making it hard to setup Microsoft email for use with Chatwoot.
Until last week the guide implied (at least from the screenshots) to setup with multi-tenancy access when you register your Azure Application. If you only want to support email inboxes at a single domain, time-consuming organisational verification is not required. The guide being is updated to make 'single tenancy access' recommended, and to explain whats involved if you want multi-tenancy. This was approved recently, and as time of writing is now live! 🙌
chatwoot/docs#389
Setup as single tenancy access generates an error in the server logs, like this:
[Your Application] is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.This is occuring as currently chatwoot hardcodes a url endpoint that includes '/common' but for single tenancy access apps, this needs to be set to the project name.
We're glad to report, we've patched this ourselves and have this working, our devs unfamiliarity with your test suite has meant the PR has no tests currently, but we hope this makes it easy for someone to take it from here.
We have this working in #6728
While Microsoft said that SMTP can be used once Oath2.0 connectivity is setup (via registering your own Azure application), seems that this is not the case and SMTP remains broken for sending emails.
The issue here is that if not using a verified app, ALL SMTP functionality stops working and that equivilent functionality needs to be reimplemented using Micrsofts Graph API.
We have this working in #6728
We're looking for someone to add tests to the PR and to get it merged in.
CW-1400
The text was updated successfully, but these errors were encountered: