Request to Azure Resource Manager failed with error

Question

Request to Azure Resource Manager failed with error

WEI ANG 25

I cannot save the flow, it always has this message "Request to Azure Resource Manager failed with error: '{"Code":"","Message":"Name new_sharedcommondataserviceforapps_fb7d8 did not match validation regex ^[a-zA-Z0-9\-\.]{1,96}$","Target":null,"Details":[],"Innererror":null}'."

It was fine yesterday, and i deleteed all the flows, reconnect the connector, log out and in again, it still happend the same, i dont know what is wrong with this non-human languages

Please help!

Thanks

Suchitra Suregaunkar 4,045 Reputation points Microsoft External Staff Moderator

2025-08-28T07:56:12.7633333+00:00

Hello WEI ANG,

Thank you for posting your query on Microsoft Q&A portal.

The error message indicates that your resource name new_sharedcommondataserviceforapps_fb7d8, does not match the validation regex pattern which is ^[a-zA-Z0-9-.]{1,96}$. This means that the name must consist of only alphanumeric characters, dashes, and dots, and it cannot exceed 96 characters. So please try the below suggested steps and retry again:

Rename the Resource: Ensure that the name you are using complies with the allowed characters. You can try using a name that contains only letters, numbers, dashes, or dots.

Check for Hidden Characters: Sometimes, copying and pasting names can introduce hidden or special characters that are not visible. Try typing out the name manually.

Review Character Limit: Make sure the name does not exceed the character limit of 96 characters.

Test with a Different Name: If renaming doesnot work, try creating a new resource with a completely different name to see if the issue persists.

Look at Dependencies: Since you mentioned that everything was fine yesterday, consider whether any recent changes might have affected the flow configuration or naming conventions.

Thanks,

Suchitra.
Agustin Pina 15 Reputation points

2025-08-28T12:51:37.8933333+00:00

I'm having the same issue here! Since yesterday, all of a sudden.

The real problem is in the logical name of the connection, which we don't choose and can't edit.

5 answers

Your answer

Suchitra Suregaunkar 4,045 Reputation points Microsoft External Staff Moderator

2025-08-28T07:56:12.7633333+00:00

Hello WEI ANG,

Thank you for posting your query on Microsoft Q&A portal.

The error message indicates that your resource name new_sharedcommondataserviceforapps_fb7d8, does not match the validation regex pattern which is ^[a-zA-Z0-9-.]{1,96}$. This means that the name must consist of only alphanumeric characters, dashes, and dots, and it cannot exceed 96 characters. So please try the below suggested steps and retry again:

Rename the Resource: Ensure that the name you are using complies with the allowed characters. You can try using a name that contains only letters, numbers, dashes, or dots.

Check for Hidden Characters: Sometimes, copying and pasting names can introduce hidden or special characters that are not visible. Try typing out the name manually.

Review Character Limit: Make sure the name does not exceed the character limit of 96 characters.

Test with a Different Name: If renaming doesnot work, try creating a new resource with a completely different name to see if the issue persists.

Look at Dependencies: Since you mentioned that everything was fine yesterday, consider whether any recent changes might have affected the flow configuration or naming conventions.

Thanks,

Suchitra.
Agustin Pina 15 Reputation points

2025-08-28T12:51:37.8933333+00:00

I'm having the same issue here! Since yesterday, all of a sudden.

The real problem is in the logical name of the connection, which we don't choose and can't edit.

Answer 1

Allen Real 20

I encountered this issue today when I tried changing connection references. Are you using the New designer feature? If yes, try to disable it, then save your flow again. That's what worked for me.

Tate Butler 0 Reputation points

2025-09-04T09:20:27.81+00:00

I also have the same issue as this post, but because it is a new flow I cannot save it, meaning when I disable the new designer all my actions will be gone.
Lam, Binh 0 Reputation points

2025-10-10T01:26:42.09+00:00

I had the exact same issue and switching New Designer off helped. Thanks!

Answer 2

Thank you for asking this question on the Microsoft Q&A Platform!

Error meaning

Azure Resource Manager validates resource names using a regular expression: ^[a-zA-Z0-9-.]{1,96}$

Which means underscore (_) is not allowed.

Your flow name new_sharedcommondataserviceforapps_fb7d8 contains an underscore (_), which violates this rule.

How to Fix It

Rename your flow to remove the underscore. For example:

new-sharedcommondataserviceforapps-fb7d8

or

new.sharedcommondataserviceforapps.fb7d8

Once renamed, try saving the flow again.

Please Accept the answer if the information helped you. This will help us and others in the community as well.

Thank you

Answer 3

Agustin Pina 15

I'm having the same issue here! Since yesterday, all of a sudden.

The real problem is in the logical name of the connection, which we don't choose and can't edit.

Screenshot 2025-08-28 at 9.51.02 AM

Damian Marquez 0 Reputation points

2025-08-28T18:10:10.15+00:00

@Suchitra Suregaunkar Can you share the process to rename the Connections? I beleive they are automatically create by PowerAutomate and we can't change the name.

We are blocked with our team and we need to solve this ASAP.

Thanks in advance

Regards

Answer 4

Allen Real 20

----- REMOVED -----

Answer 5

Victoria Greenslade 0

I am having the same problem. There are no underscores in my environment name, flow name or even in my referenced tables and yet, I'm getting the same problem:

Request to Azure Resource Manager failed with error: '{"Code":"","Message":"Name aerodev_sharedcommondataserviceforapps_991be did not match validation regex ^[a-zA-Z0-9\-\.]{1,96}$","Target":null,"Details":[],"Innererror":null}'.

I did not select this flow name, nor am I able to edit it. I'm also unable to save my progress in order to try turning off the New Designer toggle... looks like I'll be starting over.

Victoria Greenslade 0 Reputation points

2025-08-29T18:25:12.1233333+00:00

Recreating the flow in classic designer worked - so there's definitely a bug with the New Designer. Thank you Allen Real for suggesting this!

Share via

Request to Azure Resource Manager failed with error

5 answers

Your answer