PPPC-Utility VS macOSLAPS

You will likely further down the road when you have the basics setup need this tool https://github.com/jamf/PPPC-Utility This is a very useful tool to create configs that allows you to deploy app permissions so the end user does not have to allow things. For example you could create a profile that gives Microsoft Teams camera and disk access for sharing files so it does not nag the user to allow it.

For other permissions, check out PPPC Utility from Jamf: https://github.com/jamf/PPPC-Utility

we're currently using Jamf Connect and Intune to enroll our Mac´s. For the privacy settings, we're using the PPPC-Utility from Jamf. Now the question: After applying these PPPC-Profiles the silders (In Privacy Settings) are still turned off, but it seems to work. Is this behavior normal?

LAPS isn't natively supported but once again there's a third-party solution

As others have mentioned, a second account with admin privileges might be your best bet. If you're going to go that route, you may want to implement macoslaps along with that. Macoslaps randomizes the local admin password which comes in handy if you need to give the password to someone. It used to be only for Active Directory joined Macs but now can be used without an active directory (via MDM). Here's the link for more info: This goes on the clients - https://github.com/joshua-d-miller/macOSLAPS

We use MacOSLAPS on our Mac clients to randomize the admin password on those machines: https://github.com/joshua-d-miller/macOSLAPS

And that implementation is why when I set this up at $oldJob I set the RemovePassChars key to all ambiguous characters I had run into on the Microsoft product.

I believe setting something like macOSLAPS up will also resolve the issue since the automatically created local account would authenticate and update it's password silently.

There are a variety of alternatives, such as https://github.com/joshua-d-miller/macOSLAPS