I'd suggest looking into Activators to stream pipeline failures to alerts. You can get pretty granular with rules, and it supports both emails and teams messages as actions. I think these are relatively new, so might not have been available at the time this was submitted.
Here's the MS link for the documentation:
https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-introduction
The activators will give you direct access to things like the workspace name, with nothing more than a click.
But, just so you are aware, it is also possible to use sempy.fabric to programmatically identify workspace names and objects. You shouldn't store a static list which would need to be maintained.
https://learn.microsoft.com/en-us/python/api/semantic-link-sempy/sempy.fabric?view=semantic-link-python
Recent ideas
Dedicated Fabric Message Center to communicate planned Fabric Changes
Summary Microsoft recently rolled out a change that automatically enabled the Item Recovery tenant setting in Microsoft Fabric for tenants where the setting had not been explicitly configured. Accor...Edgar_10 hours agoNew MemberNew33Views5likes0CommentsWorkspace-Level Control of Storage Modes (Import vs DirectQuery vs Direct Lake)
Organizations operating under strict governance and data residency requirements need the ability to control which storage modes are permitted within a workspace. Currently, report authors can choose...masoodaftab10 hours agoNew MemberNew6Views0likes0CommentsGranular Workspace Permissions Beyond Workspace Roles
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } The current workspace access model is limited to the predefined workspac...masooddevcorp11 hours agoNew MemberNew20Views1like0Comments