Erwin

@dingmeng-xue the documentation specifies that the count parameter should be included too, maybe that's what is missing, it should be added by default when you call the Az.Resources module with...

Same issue found with: `New-MgApplicationOwnerByRef`, works on `1.10` with a `BodyParameter` but not on `1.11`.

Found this one too in my PowerShell Function App, it's scheduled but it gave this error only yesterday (once), it has a failure rate of 0.7%, not sure what the...

@gocha thanks! It's not just SQL dependencies, also servicebus dependencies are affected and solved the same way, by downgrading every reference to work with System.Diagnostics.DiagnosticSource 4.7.0. in My case I...

@ankitkumarr I see you provided a (possible?) fix. Can you update us on the status?

Same here, also it would be nice to customize this as a template, i see no option for that now under `Microsoft.ApiManagement/service/templates`

What works for me (only works on local, this will throw errors on portal): Don't reference to appsettings directly, instead; reference to the parameters.json first like: `@{parameters('WORKFLOWS_SUBSCRIPTION_ID')} ` Then reference...

In fact, using `@appsettings` at all (deployed in Azure) for the identity element will not work (not from connections.json and not from parameters.json if you first make it a parameter...

This product is definitely manageable. I think the main issue is that logic apps itself is trying to be the simplest thing imaginable in Azure. Yet it truly is one...

> Hello @erwinkramer you can have a look here to see if System assigned identity is enable or not.  I don't have it enabled but I'm also running locally...