Chrome 142 LNA Restrictions: Integration iframes require allow="local-network-access"

[unadlib]

Chrome 142 restricts the ability to make requests to the user's local network, gated behind a permission prompt.

This restricts the communication methods for some of our MS Teams integration plugins that interact with local applications. This means the iframe provided by MS Teams for third-party integrations will need to include the allow="local-network-access" attribute. Otherwise, we will be unable to prompt the user to grant permission for these local network requests.

We would like to know if the official MS Teams team plans to add the allow="local-network-access" attribute to the MS Teams integration iframe.

Related documentation:

https://developer.chrome.com/release-notes/142#local_network_access_restrictions
https://developer.chrome.com/blog/local-network-access
https://docs.google.com/document/d/1QQkqehw8umtAgz5z0um7THx-aoU251p705FbIQjDuGs/edit?tab=t.0#heading=h.v8oobsqxbxxy

[Nivedipa-MSFT]

@unadlib - Thanks for bringing this issue to our attention. We will check this internally to determine if there are plans to add the allow="local-network-access" attribute to the MS Teams integration iframe.

[unadlib]

hi @Nivedipa-MSFT, Thanks so much for your reply.

If you have any updates, please let us know as soon as possible. This is crucial for our MS Teams integration app.

[pratzoncode]

Hi @Nivedipa-MSFT
Any updates on adding the allow="local-network-access" to the MS Teams integration iframe?
We have more than 100K users (who are also power users of Microsoft Teams) that will be impacted if Microsoft does not add this parameter soon to the iframe.

If there is a channel we can escalate this, please let us know. This is really critical to us. Thanks!

[pratzoncode]

Hello @Nivedipa-MSFT Following up on our above request. Could you provide some acknowledgement or response please?
We will have a large volume of Microsoft Teams users impacted if your team does not respond

[Nivedipa-MSFT]

Hello @pratzoncode - Engineering team is evaluating the addition of LNA support; however, there is currently no confirmed ETA. We will keep you informed as soon as we receive any updates on the timeline.

[u9520107]

@Nivedipa-MSFT
I am not sure if there are information regarding this, but will these LNA restrictions come to the webviews for the MS Teams desktop apps?
And if they are, how do we prepare our apps for that?

Thanks!

[Nivedipa-MSFT]

@u9520107 - We are checking this with engineering team, we will update you once we get any input from them.

[bumasankarra]

@Nivedipa-MSFT
This issue affects our MS Teams integration as well. Our workaround currently is to disable the chrome://flags/#local-network-access-check flag. This is a temporary flag and will be removed in Chromium v147 (around March - April 2026) and disabling LNA check will no longer be possible.

https://issues.chromium.org/issues/461326116
https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/flag-metadata.json;l=6811-6817

[sk1519]

@Nivedipa-MSFT This is a huge impact on our customer base. Our customers depend on our embedded iframes in Microsoft teams product to access our product and without these iframes they are completely blocked.

Is it possible to escalate this issue? Kindly let us know.

[Nivedipa-MSFT]

@sk1519 - Could you confirm if your app is currently available in the Teams catalog? If it is, please share the app's name, so we can coordinate with the engineering team about enabling LNA for this app through ECS list.

[unadlib]

hi @Nivedipa-MSFT ,

Could you please help coordinate with the engineering team to enable LNA for the following five apps through the ECS list?

Thank you very much.

---

RingCentral
TELUS Business Connect
Avaya Cloud Office
AT&T Office@Hand
BT Cloud Work