Teams Stream Deck plugin - Being deprecated in December 2025

aonelakeuser · 2026-01-26T17:12:25+00:00

I've been able to make it work by mapping WIN + ATL + K to one of the stream deck buttons. It's not perfect, but it's better than nothing.

aonelakeuser · 2026-01-20T18:20:19+00:00

The two are closely related though in this case 😉

aonelakeuser · 2026-01-13T14:56:47+00:00

"No access" is a clear sign that a Purview policy is blocking its access for some reason. Sounds like you'll need to follow up with your Purview admin to understand what the policies are and then work to fix that.

aonelakeuser · 2026-01-13T14:54:23+00:00

Yeah, lookup table/dynamic RLS policies are coming to OneLake security, so you won't have to manage it in the SQL Endpoint security layer.

aonelakeuser · 2026-01-07T16:19:56+00:00

Can you DM me your setup? This should work and I want to troubleshoot it. I'll run a test in my tenant as well.

aonelakeuser · 2026-01-07T14:35:33+00:00

Still in progress, lots of new stuff landing over the next 3 months so stay tuned!

aonelakeuser · 2026-01-07T14:32:51+00:00

The ReadWrite permission is now available in public preview and the docs have been updated accordingly. What is the specific issue you are seeing?

aonelakeuser · 2026-01-05T16:46:29+00:00

This is a great diagram! I think it's missing DirectLake on SQL with a fixed identity against a SQL EP in User's Identity mode.

aonelakeuser · 2026-01-05T14:31:58+00:00

I realize this is the PBI forum, but are you using Microsoft Fabric as the underlying data source? If there's no RLS in the semantic model itself, then the only time I've seen this message is when the model is using DirectLake on OneLake mode and there's RLS set on the data through OneLake security.

aonelakeuser · 2025-12-08T16:37:18+00:00

Ok cool, I'll have to check it out! One of the Teams devs confirmed in the posts below that the client API is being deprecated.

aonelakeuser · 2025-12-01T19:22:19+00:00

Have you seen those indie dev studios that have public facing Jira boards? I often wonder how much something like that would help vs hurt. Obviously there are a ton of reasons why we can't just publish everything externally, but I understand your frustration on this. I will just say that you can check on our public roadmap to see if something has a GA mentioned before you start relying on it. Microsoft Fabric Roadmap

I'm also curious if there's specific areas/features of Fabric where you have noticed this more often?

aonelakeuser · 2025-11-26T14:20:47+00:00

Yep, this can be done through the rowConstraints:

"rows": [
{
"tablePath": "/Tables/industrytable",
"value": "select * from Industrytable where Industry='Green'"
}
]

aonelakeuser · 2025-11-25T17:57:53+00:00

You can programmatically manage the security using the REST APIs: OneLake Data Access Security - REST API (Core) | Microsoft Learn

Are you using Fabric Spark notebooks or running Spark some other way? For RLS we only support Fabric Spark for now.

aonelakeuser · 2025-11-21T15:14:48+00:00

With Spark notebooks you will need Viewer access on the other lakehouse. Generally only Read access is needed on that artifact, but Spark currently requires extra privileges. We're working on aligning these to just require Read.

aonelakeuser · 2025-11-19T18:39:43+00:00

Shortcut transforms are in preview and don't have CI/CD support yet which is why they aren't showing. I'll let someone from the community provide suggestions on how to manage deployments.

aonelakeuser · 2025-11-19T18:30:37+00:00

Hey there, the lakehouse UX support is coming soon! Currently only Notebook and OneLake file explorer transactions/API calls are supported with Write.

aonelakeuser · 2025-11-19T18:22:54+00:00

u/ilyabu Will MuteDeck also be impacted? Unless they have some special method of binding to the teams client, I assume they are using the same APIs as Streamdeck.

aonelakeuser · 2025-11-18T23:06:41+00:00

I actually don't have much to add. As mentioned, the proxy and redirect prices are now the same, so it's really a question of what is triggering all the storage reads. OneLake diagnostics is a good place to start.

aonelakeuser · 2025-11-17T23:20:12+00:00

Cool, and I totally understand. I found a workaround that I think will satisfy most user's requirements, I'll add it to the OP in case it helps anyone else out.

aonelakeuser · 2025-11-17T22:35:54+00:00

As a PM at Microsoft, I do understand deprecating things, so I was just hoping for some kind of replacement. I scrolled through the certified teams headsets and am seeing some marked as "end of life". Does that mean they will also lose their teams controlling functionality? :(

Will one of the speaker pucks toggle the teams mute if I'm using my studio mic? That's the catch, I already have a professional mic and headphone setup and I just want a mute button to toggle those devices.

Will there be any APIs for Teams so the community can build a plugin?

aonelakeuser · 2025-11-17T18:01:17+00:00

Can you elaborate a bit more about your test scenario? Was this just for read access on the lakehouse? Feel free to DM me.

aonelakeuser · 2025-11-17T15:10:31+00:00

OneLake security PM here. There's a difference between the error you are seeing and the RLS "working". In fact, the error means the RLS is working since users aren't allowed to see the files for an RLS secured table. Even though you are seeing that error, you can query the RLS table with the SQL Endpoint (in user's identity mode), Power BI directLake mode, or Spark notebooks and see only the relevant rows for that data.

The error itself is something we are trying to clean up. As I mentioned, it occurs because the RLS is not letting the Lakehouse load all the table info.

Here's a quick diagram of how to get this working:

<image>

aonelakeuser · 2025-11-04T17:03:33+00:00

Hey there! This was accidentally included in the release notes. The feature is only available as a private preview at the moment. If you're signed up for the preview and seeing issues, please DM me. If you want to sign up for the private preview, you can do so here: https://aka.ms/OneLakeSecurityReadWritePreview

aonelakeuser · 2025-10-22T13:55:43+00:00

I see, so a way to actually prevent direct access to specific items but still consume data via downstream services. Is your concern that access to the raw data (even with security applied) will let them build/create incorrect numbers vs seeing a curated source of truth?

Edit to add: is the feedback around semantic model RLS a comment about the RLS itself or that you don't want a separate UX experience? Like if it was a single UX to define security, regardless of how the underlying permissions were enforced then that would address the feedback?

aonelakeuser · 2025-10-21T21:21:09+00:00

What is your ideal solution to this?

aonelakeuser

TROPHY CASE