Unanswered

PA Desktop interfering with 802.1X

(1) Share

Report

Posted on by networkicecream

We use 802.1X with certificates for network authentication. If a machine has PA Desktop installed then the RADIUS server sees the username "uiflows.gov.flow.microsoft.us" connect to the network and access is denied. If the user uninstalls PA Desktop it will work again.

I'm on the network team, trying to get others to ask Microsoft support, but I thought someone here might know how to make PA Desktop butt out of the 802.1X conversation so Cisco AnyConnect can do it's thing.

Thank you

PS. Apologies for the inappropriate label but I picked the most general forum I saw and a label is required even though there isn't an appropriate one. Mods can move the question wherever they think most appropriate. Thanks

Categories:

Power Automate Desktop

All responses (5)

Answers (0)

Sort by

fless1 55 on at

Like
a
(0)

Report
Copy link

Link copied!

did you get anywhere with this please as it seems my company has same issues with PA
networkicecream 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Not really. We only had a few people using PAD and they ended up uninstalling and using the web version.

I can't find any notes but I also remember a similar 802.1X issue where had a few people where we ended up finding a cert in their personal store (in Cert Mgr) that was interfering with the cert that 1X used. I wondered at the time whether PAD might be a similar situation where we could find the cert and remove it (possibly re-adding it in case the order is the problem).

If you come up with solution please post it as I'm sure this will come up for us again eventually.
chimpoo 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Microsoft Team,

Can we get support on this? We also saw the exact same issue in our environment. Machines that had 'power automate for desktop' application were interfering with the dot1x process and were causing the machine to present the wrong certificate on the wired ethernet interface. Once this app is removed from the machine, it fixed our issue

Thanks
rguptaMB 12 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello, Did you find solution/workaround to this issue? I am also having same issue from couple of months with PAD.
momlo 1,527 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @networkicecream

UI Flow service connects to Azure Service Relay to obtain any new jobs that might be waiting for it to execute/send logs/send the status of flow that finished executing/other operations. This service runs as a NT SERVICE\UIFlowService user, not the regular windows account/person. So this is probably what you are seeing.

Note this is part of the "machine runtime" module of PAD.

Take a look here:

https://learn.microsoft.com/en-us/power-automate/desktop-flows/pad-architecture

If the person wants to develop flows but not schedule/run flows from the web portal, you might skip the "machine runtime" installation.

Then if you would like to have these flows executed automatically/run on a dedicated server/machine, you alter the configuration of this server/whitelist the user.