Prevent users from disconnecting AOVPN user tunnel

Mousefluff 

You asked Microsoft to rewrite the default interface to suit your needs, which is not going to happen

You are starting to understand the point of this post. IF there is not administrative way to control this element of the UI, as there is with many parts of the UI, then it does need an element of control. I am hearing this from many customers of all sizes. This is the beginning of the route to enacting positive change in the platform and how many things have been improved over the years. I was also hopeful that someone else who has also spent the time digging into this area might have found a specific ACL on a registry key or a hidden registry setting that controls access to this element such as a registry setting that doesn't exist but changes behaviour when created.

In the second post I put a link to a feedback hub item created asking to make this a manageable setting, as many others have one in the past with other items that need to be brought into the scope of management. This is exactly the way we, as users, administrators, and consultants, help Microsoft to improve things so they work better for more. To say otherwise is to speak for the whole of Microsoft and rebuke all features requests.

 then you mass reported my account and it was locked up for some period of time

As there was no way to prevent additional derailing of the thread and no apparent change in behaviour change when repeatedly informed that either the question had been misunderstood or that the input was not related to the question and the forum doesn't allow thread starters to remove unhelpful responses it seemed that option had the desired result in getting the thread back on track so others with helpful insight might be able to provide input.

You have 3 choices really: Make your own app ( learn how to code. ) Choice #2: Learn how to write scripts to bypass the limitations with the default UI Choice: #3: Use a 3rd-party solution

none of those answer the problem. The point of this thread is to identify any undocumented methods of controlling the 'connect automatically' option on the client VPN UI as I have already explored option 2. Option 1 doesn't apply as we are talking about a closed Microsoft solution "Always On VPN". Neither does options 3 as the entire point of this is the need to use AOVPN for many organisations due to dependencies with autopilot, integration with Intune management etc.

this is all industry-standard, and I'm not going to say anything else. I already explained how the VPN works.

you did largely talk about genuine topics around VPN infrastructure and a lot of that information was technically accurate. It was, however, the equivalent of giving a detailed description of how the internal combustion engine works when being asked about the seatbelt warning light controls.

Personally, when it seems evident i have misunderstood somethign i have been told I would re-examine any initial assumptions and the scope of what is being asked rather than doubling down and ignoring what is being asked.