web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Unable to Create SEV1 ...
Power Automate
Suggested Answer

Unable to Create SEV1 IcMs using connector

(1) ShareShare
ReportReport
Posted on by Microsoft Employee
Hello Team,
 
I would like to understand which severity levels are currently supported when creating incidents using the IcM Connector.
 
Earlier, I was able to create Sev1 incidents via the IcM connector in Power Automate. However, I am now encountering the following error:
"Failed to create incident: Severity < 2 is not allowed."
 
I also attempted with Sev2 but faced the same issue, whereas Sev4 worked successfully.
 
Could you please confirm if there have been any recent changes to the connector that restrict the creation of incidents with severity levels below Sev2?
Please let me know also what is required to create sev1 Icm directly
 
Thanks in advance.
Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,318 Moderator on at
     
    This is not a flow issue. The error Severity < 2 is not allowed clearly indicates that Sev0 and Sev1 are being blocked at the connector/backend level. Sev3/Sev4 continuing to work confirms this is a policy check.

    In most enterprise setups, Sev1 creation is intentionally restricted because it triggers on-call paging, SLA tracking, and high-severity escalation workflows.
    Because of that, automation via standard connectors is often limited to lower severities.

    If Sev1 creation is required, you will likely need:
    • explicit allowlisting or special permissions from the IcM/service team, or
    • a different API/service path with elevated access
    A practical workaround is to use a gated escalation approach:
    • create a Sev3 via flow
    • then upgrade to Sev1 through an approved process or manual/controlled step
    Would be helpful if the IcM team can confirm whether this restriction was recently enforced at the connector/API level.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard