Inconsistent Zoom meeting URLs prevent Teams Rooms from joining meetings | Community
Skip to main content
Explorer
July 21, 2026
Question

Inconsistent Zoom meeting URLs prevent Teams Rooms from joining meetings

  • July 21, 2026
  • 5 replies
  • 126 views

We have identified an inconsistency in how Zoom meeting join URLs are generated depending on the method used to create the meeting. This inconsistency affects our Microsoft Teams Meeting Rooms' ability to join Zoom meetings.

Currently, there are several ways to create a Zoom meeting:

  1. Zoom Workplace
  2. Classic Outlook with the Zoom plugin
  3. New Outlook with the Zoom add-in
  4. Zoom Web Portal

In all four cases, the Zoom meeting URL is automatically populated in the meeting's Location field.

Within our organization, meeting invitations are forwarded to Microsoft Teams Meeting Rooms. For privacy reasons, our mailbox processing removes the meeting body (notes) but retains the Location field. As a result, the Teams Room relies on the meeting URL stored in the Location field to join the meeting.

The issue is that the URL format differs depending on how the meeting was created.

Zoom Workplace / Classic Outlook plugin

https://domain.zoom.us/j/98047338034?pwd=... .1

New Outlook add-in

https://domain.zoom.us/j/98047338034?pwd=... .1&from=addon

Zoom Web Portal

https://domain.zoom.us/j/98047338034?pwd=... .1&jst=1

Our testing shows that:

  • URLs generated by the New Outlook add-in and the Web Portal work correctly, and Teams Rooms are able to join the meeting.
  • URLs generated by Zoom Workplace and the Classic Outlook plugin do not work. Teams Rooms report that the meeting details are incomplete.
  • If the same URL is manually edited to append either &from=addon or &jst=1, the Teams Room is able to join successfully.

This suggests there is an inconsistency in the generated meeting URLs that affects interoperability with Microsoft Teams Rooms.

This has a significant impact on our organization. Because users create meetings using different Zoom clients, we cannot enforce a single creation method. Many users naturally use their preferred workflow, and less technical users are unlikely to manually modify meeting URLs. As a result, meeting room join reliability is inconsistent, which discourages our staff from using Zoom and prevents us from recommending Zoom as a supported meeting platform, despite requests from employees to use it instead of Microsoft Teams.

Has anyone found any workarounds to this issue

    5 replies

    Employee
    July 28, 2026

    Hey ​@Vasileios Roidis 

     

    Thank you for reaching out. We suggest you submit a Technical Support ticket here with the details so our Technical Support Team can assist further.

    Explorer
    July 28, 2026

    I laready have raised this with support, and they pointed me to both the feedback channel and the Zoom community. The request has been resolved as they don’t see this as a technical issue, but rather a feature. 
    “Your request (TS2378405) is now marked as solved.”

    Employee
    August 3, 2026

    &from=addon or &jst=1 is not essential for a zoom meeting link, so it could be related to the way Microsoft Teams Meeting Rooms parses meeting links. Specifically, it could be due to kind of solid template or body content rules required by Microsoft Teams Meeting Rooms. We recommend to check with Microsoft Teams support for that. 

    Explorer
    August 3, 2026

    @DalongChen, if “&from=addon or &jst=1 is not essential for a zoom meeting link” as said, why are they there in the first place?
    More importantly (and this is my question) why are they there when a meeting invite is created in one way, and missing when a meeting invite is created in another way?

    As stated in TS2378405, going to Microsoft with this issue, will generate a similar response: “our MS teams client is working with some link formats, and not with others, we’d recommend to check with Zoom support and have them standarise their link format across all their solutions”.

    I don’t see an issue with Microsoft, MS Teams is consistent on its end: 
    if “&from=addon” or “&jst=1” is present it works,
    if “&from=addon” or “&jst=1” are missing it doesn’t work. (and if i manually add it, it does work)
    What I do see, is that these links are not consistent when being generated by Zooms applications/tools/extensions. This inconsistency on your end, is why i have raised this with you guys and not with Microsoft.

    thanks,
    Vasileios

    Employee
    August 7, 2026

    @Vasileios Roidis Both &from=addon and &jst=1 are additional flags only to trace either how a zoom meeting is created (zoom client, web portal, outlook add-in, chrome extension, etc) or where our customers join a zoom meeting from (zoom client, web portal, outlook calendar event, etc). A zoom meeting link like https://domain.zoom.us/j/1234567889?pwd=xxxxxxx without &from=addon and &jst=1 should just work. You can verify that by trying either zoom client or zoom web client (PWA client).