In certain cases it is advisable to adjust the power settings of Windows devices so that they always remain on and do not lock themselves automatically. Of course, this setting should only be made for non-critical devices to avoid logging in again. Such situations arise, for example, with POS systems or shared workstations with anonymous users and access to non-critical data.
Of course, we can create the "Always On" energy policy with Intune and distribute it to our devices.

Intune Power Policy - Settings Catalog

We can do the whole thing very easily with one Settings catalog Create policy in Intune.

First create a new policy under:
Devices> Windows> Configuration profiles

Intune, Settings Catalog Profil erstellen

We then give the guideline a meaningful name such as "WIN-EnergyAllwaysOn" and optionally a description:

Intune, Profil Name und Beschreibung

Then you have to add a few settings, these are the following:

  1. When plugged in, turn display off after (seconds)
  2. Turn off the display (on battery)
  3. Turn off the display (plugged in)
  4. Require a password when a computer wakes (on battery)
  5. Require a password when a computer wakes (plugged in)
  6. Specify the system sleep timeout (on battery)
  7. Specify the system sleep timeout (plugged in)
  8. Turn on the ability for applications to prevent sleep transitions (on battery)
  9. Turn on the ability for applications to prevent sleep transitions (plugged in)
  10. Select an active power plan
  11. Prompt for password on resume from hibernate/suspend (User)
  12. Turn Off the Hard Disk (seconds): (Device)
  13. Turn Off the hard disk (on battery)
  14. Turn Off the hard disk (plugged in)
  15. Device Password Enabled
  16. Select Lid Close Action On Battery
  17. Select Lid Close Action Plugged In

The easiest way to find the individual settings is to search for them:

Intune, Settings catalog Settings hinzufügen

Finally, you assign the guidelines to your target group and that's it.

If you have a second energy policy, don't forget to exclude the policy assigned here in this one, not that there are any conflicts: