What does the video show?
In the video, we present how a deployed device in Essentials MDM can be managed using two mechanisms:

• policies, which define the rules that apply to the device,
• actions, which can be performed immediately on a specific phone.

The entire process is shown using the example of a Samsung phone deployed in COBO mode, meaning the fully managed corporate device model. Thanks to this, the administrator has broad capabilities to influence the phone’s settings and perform remote actions.

The material shows:

• how to check which policy is assigned to the device,
• how to go to the full management policy,
• how to block the camera from the security settings,
• how to send an informational message to the phone,
• how to remotely wipe the device and restore it to factory settings.

This is a very practical scenario because it shows both ongoing security rules and actions that the administrator can trigger immediately.

Policies and actions in Essentials MDM – step by step

1. Selecting a previously deployed device
   The process begins by going to the list of devices in Essentials MDM.

In the video, a previously added Samsung phone is used. It is this device on which the subsequent actions related to policies and actions are demonstrated. From the very beginning, the material focuses not on deploying the phone, but on managing a device that is already operating in the environment.

2. Checking the assigned policy
   The next step is checking which policy has been assigned to the device.

The table shows that the phone is using the default policy. The device was deployed in COBO mode, which means full management of a corporate-owned device. Thanks to this, the administrator can apply a wide range of settings and restrictions to it.

3. Going to the full management policy
   Next, the user goes to the policies assigned to the device.

The material shows the path leading to the full management policy and then to the security options. This is where it is possible to define which device functions should be available and which should be blocked.

4. Policy example – blocking the camera
   The video shows a practical scenario in which the administrator wants to block the camera on the phone.

First, we see that the camera works properly and can be launched normally. Then the administrator searches for the appropriate function in the settings and enables the camera block in the policy.

After saving the changes and refreshing the policy, the effect appears directly on the device. When the user tries to launch the camera, the application is closed, and the user sees a message informing them that security settings do not allow the use of this function.

This is a simple but very clear example showing how a security policy translates into the actual behavior of the phone.

5. Policies as rules applied to devices
   At this stage, the video emphasizes an important distinction – policies are used to define rules that should apply to devices.

In practice, this means that the administrator can create top-down settings for entire groups of devices or for specific deployment types. Camera blocking is only one example – there are many more possibilities.

6. Going to actions performed on a specific device
   In the second part of the material, another type of operation is shown – actions performed directly on a single device.

The administrator goes to the phone details and selects the More Actions menu. This is where the operations are available that do not change the general policy, but allow a specific action to be performed on the selected device.

7. Sending a message to the phone
   The first example of an action shown is sending a message to the device.

The administrator selects the Send Message option, enters the message content, and sets the way it will be displayed. In the example shown, a full-screen informational message is used.

After a moment, the message appears on the phone. The user must read it and confirm it with the OK button before they can continue using the device.

This is a very practical function in situations where the company wants to quickly provide the user with important information directly on the phone screen.

8. Remote device wipe
   The next action shown is wiping the device, meaning remotely restoring it to factory settings.

The video presents a practical scenario in which the organization wants to stop using the phone, remove data from it, or protect itself in the event of the device being lost or stolen.

This is an operation that requires additional confirmation with the administrative password. Once it is performed, the phone is wiped and restored to factory settings.

This is one of the most important actions available from the MDM level, because it allows the organization to react immediately in situations related to the security of corporate data.

9. The difference between policies and actions
   At the end of the material, the main difference between these two mechanisms is clearly highlighted.

Policies are responsible for rules that should apply to devices in a consistent and ongoing way.
Actions make it possible to perform a specific operation immediately – here and now – on the selected device.

This distinction is very important from the perspective of day-to-day mobile environment management.

Why are policies and actions useful?
The combination of policies and actions in Essentials MDM gives the administrator a great deal of flexibility in managing corporate devices.

The main benefits of this approach are:

• the ability to centrally define security rules,
• quick blocking of selected device functions,
• the ability to respond to individual operational situations,
• convenient sending of messages to the phone,
• remote wiping of devices in risk situations,
• better control over the corporate mobile fleet.

In practice, this means that the organization can both maintain consistent security standards and respond to current needs related to specific devices.

What should you pay attention to when working with policies and actions?
Although the way they work is simple, it is worth remembering a few important points:

• the scope of available actions depends on the device deployment model,
• in COBO mode, administrative capabilities are greater than in more limited scenarios,
• policies affect device behavior on an ongoing basis,
• actions work immediately on a specific phone,
• operations such as wiping a device may require additional administrative confirmation,
• before performing an action, it is worth making sure that it applies to the correct device.

This makes it easier to use the available functions safely and avoid operational mistakes.

Summary
The video shows that policies and actions in Essentials MDM are a practical tool for day-to-day management of mobile devices.

Using the example of a phone deployed in COBO mode, we see how the administrator can:

• block the camera by changing the security policy,
• send a message directly to the device,
• remotely wipe the phone and restore it to factory settings.

This is a practical resource for organizations that want to better control corporate devices and effectively enforce security rules from a single console.