Does SCOM 2025 Teams Channel Integration required to have Run As Profile ?

Hi Mitan,

this isn’t a bug in itself – it’s how the native Teams connector is wired in SCOM 2022/2025.

The Run As Profile dropdown in the Microsoft Teams channel only shows Run As profiles that live in the “Notifications Internal Library” management pack and are configured for the Teams/Graph scenario. Simply mapping your Run As account to the built-in “Notification Account” profile isn’t enough for that dropdown to be populated.

In SCOM 2025 the documented prerequisites for Teams still talk about a Run As account using Simple Authentication (formerly called Basic) with a Teams-licensed Entra ID user, and the Notification Account Run As profile is what SCOM uses to send notifications.

The Teams channel UI then expects an extra notification Run As profile defined in the Notifications Internal Library.

Why your dropdown is empty

The dropdown will be blank when:

• There is no Run As profile stored in the “Notifications Internal Library” MP that SCOM recognises as a notification profile, or
• The profile you created lives in another MP (e.g. a custom MP) and therefore doesn’t show up for Teams.

Mapping your Run As account only to the built-in Notification Account profile does not create such a Teams-specific profile automatically.

What to do

Try the following sequence:

1. Verify the Notification action account (Run As account)
   • Under Administration → Run As Configuration → Accounts, make sure you have a Notification action account of type Simple Authentication for Teams (user@domain, licensed for Teams, member of the target channel, no MFA).
     • Distribute it to the Notifications Resource Pool.
     1. Create a dedicated Run As profile for Teams in the Notifications Internal Library In the console:
        • Go to Administration → Run As Configuration → Profiles.
          • Select Create Run As Profile…
            • Give it a logical name (e.g. Teams notification profile).
              • Important: For Destination management pack, choose Notifications Internal Library. This is what makes it appear in the Teams channel Run As Profile dropdown.
                • On Run As Accounts, click Add, pick the Notification action account (or create a new Simple Authentication Run As account if you prefer), and target it appropriately (typically Alert Notification Subscription server or “All targeted objects” if you’re following the docs for notification accounts).
                  • Save the profile.
                  1. Re-open the Microsoft Teams channel wizard
                     • Go to Notifications → Channels → New Channel → Microsoft Teams.
                       • On the Authentication page, enter Tenant ID and Client ID from your Entra ID app registration.
                         • The Run As Profile dropdown should now list the profile you just created in the Notifications Internal Library. Select it and continue the wizard as normal.

Once this Teams-specific profile exists in the correct MP, the dropdown populates and the connector uses that Run As account to do the delegated Graph call (ChannelMessage.Send) into your Teams channel.

So in short: it’s not really a product bug, it’s just that the Teams channel will only show Teams-compatible Run As profiles defined in the Notifications Internal Library. Creating one there (instead of only using the generic Notification Account profile) is the “workaround” and the supported configuration.

Best Regards

Stoyan Chalakov

"If my response was useful, please consider marking it as the answer. It keeps the forum clean, structured, and more helpful for everyone. Thank you for supporting the community."