NoCreateFlowBlade and ErrorLoadingExtensionAndDefintion

%3CLINGO-SUB%20id%3D%22lingo-sub-2445434%22%20slang%3D%22en-US%22%3ENoCreateFlowBlade%20and%20ErrorLoadingExtensionAndDefintion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2445434%22%20slang%3D%22en-US%22%3E%3CP%3ESeveral%20of%20us%20who%20are%20contracting%20with%20a%20company%20with%20a%20subscription%20to%20Azure%20and%20we%20recently%20got%20access.%26nbsp%3B%20Any%20time%20we%20tried%20to%20create%20any%20resource%20it%20fails%20with%20%22NoCreateFlowBlade%22.%26nbsp%3B%20If%20we%20try%20to%20create%20a%20support%20ticket%20it%20states%20%22ErrorLoadingExtensionAndDefinition%22.%26nbsp%3B%20We've%20tried%20on%20Windows%20and%20MAC%2C%20in%20Safari%2C%20Chrome%2C%20Edge%20and%20Firefox%3B%20in%20regular%20and%20in%20private%20modes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20is%20appreciated%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2445465%22%20slang%3D%22en-US%22%3ERe%3A%20NoCreateFlowBlade%20and%20ErrorLoadingExtensionAndDefintion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2445465%22%20slang%3D%22en-US%22%3ENote%20that%20our%20other%20Azure%20accounts%20work%20fine.%3C%2FLINGO-BODY%3E
New Contributor

Several of us who are contracting with a company with a subscription to Azure and we recently got access.  Any time we tried to create any resource it fails with "NoCreateFlowBlade".  If we try to create a support ticket it states "ErrorLoadingExtensionAndDefinition".  We've tried on Windows and MAC, in Safari, Chrome, Edge and Firefox; in regular and in private modes. 

 

Any help is appreciated

4 Replies
Note that our other Azure accounts work fine.
Does the issue happen if you try to create a resource using Azure CLI or PowerShell?
Does the error in the Portal - ie the JSON of the error have any more information (ie it is not a policy etc preventing you)?

Most people who seem to have this problem, indicate it was a browser client issue.

@Luke Murray Thanks for responding. This is through the portal. It might be a cert issue from the host company is my guess at this point.  I've tried every browser, several users, and several different machines.  Works fine on my core azure account.

Oh and it's not policy, but good idea, thanks