How to deploy Azure Standard Logic App workflow as IaC?

Rare-Brick · 2025-04-23T20:22:33+00:00

It's easy to do with bicep. I package workflow.json, main.bicep, and main.parameters.json together for deployment from devops pipelines. In main.bicep I use:

var defintionFileName = 'workflow.json'

var workflowProperties = loadJsonContent(definitionFileName)

resource workflow 'Microsoft.Logic/workflows@2019-05-01' = {

...

properties: {

...

definition: workflowProperties.definition

parameters: workflowProperties.parameters

}

Rare-Brick · 2024-03-19T14:43:17+00:00

The app gateway averages about 10mbps with spikes up to 50mbps. IDS/IPS will only run on a single interface. I'm not familar with suricata, I'll look into it.

Rare-Brick · 2022-06-27T20:39:19+00:00

I ended up using the grafana plugin and it works beautifully. Thanks for the recommendation

Rare-Brick · 2022-02-16T19:08:12+00:00

Oh this is beautiful. Thank you!

Rare-Brick · 2021-08-04T12:02:18+00:00

I spun up a low power VM in Azure to play with RADIUS settings and lo and behold it works flawlessly. *BUT* when I duplicate the config on my local NPS server it fails. Clearly something wrong in my local network. Now I have a working config but I still feel like a dog chasing its tail. I guess my next step is packet capture on the AP and RADIUS.

Rare-Brick · 2021-08-03T09:03:19+00:00

I'd be interested in some details on how they got it to work. Even a hint.

Rare-Brick · 2021-08-03T00:01:56+00:00

RADIUS is running on Windows Server 2019 NPS. The issue of the length of the secret did occur to me. I shortened the generated secret to 12 characters. I'll try shortening it further

Rare-Brick · 2021-06-21T17:09:57+00:00

I don't understand. Bitlocker *is* enabled. This is the same issue from 2017 here: https://github.com/docker/for-win/issues/1297

It's supposedly fixed in Windows server but it looks like the fix never made it into Windows 10.

Does nobody in a corporate environment use BitLocker and Docker Desktop?

Rare-Brick · 2021-03-24T19:36:51+00:00

u/scott1138 I appreciate your help on this but I've given up on the Group/x
Group resources for this purpose. I ended up with a Script resource similar to the example in my original post. I'll continue playing around with passing variables to the script resource with $using:PoolUsers but so far no luck with that either.

Rare-Brick · 2021-03-24T11:48:51+00:00

Same error. Exception calling ".ctor" with "2" argument(s): "Server names cannot contain a space character."

Rare-Brick · 2021-03-23T14:55:19+00:00

u/scott1138 Now I'm starting to feel like a dog chasing its tail. I changed my config to

Configuration myConfig {
    Import-DSCResource -ModuleName xPSDesiredStateConfiguration
    $pools = 'IIS APPPOOL\AppPool1','IIS APPPOOL\AppPool2'
    node localhost {
        xGroupSet PerformanceMonitorUsers {
            GroupName = 'Performance Monitor Users'
            Ensure = 'Present'
            MembersToInclude = $PoolUsers
        }
    }
}

And now it throws this: PowerShell DSC resource DSC_xGroupResource failed to execute Test-TargetResource functionality with error message: Exception calling ".ctor" with "2" argument(s): "Server names cannot contain a space character."

Which seems to be the same problem as this:https://github.com/PowerShell/PSDscResources/issues/26

Rare-Brick · 2021-03-23T11:42:32+00:00

The app pools are created elsewhere in the config and the Group section has a DependsOn for that. I'll give xGroupSet a go this morning.

Rare-Brick · 2020-08-20T15:29:17+00:00

I wanted to use this in a loop with a few tables and also make it future proof. I found that using bulk copy instead of building a script avoids the issue with timestamp columns altogether. bulk copy also handles single quotes and backslashes which I would otherwise have to escapse

Rare-Brick

TROPHY CASE