> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/documentation/deployment-sca/deployment-for-your-devices-in-intune/deployment-ios-mdm-managed-and-complaint-device.md).

# Deployment iOS MDM - Managed & Complaint Device

Implement SCA within Microsoft Endpoint Manager for you Compliant Device\
The moment a user connects with the AAD-account Access control via Azure AD Conditional Access enforces our App to require a complaint device.

### Compliance Policy

1. Login to Endpoint Manager with your Admin-Account
2. Go to Devices → Compliance policies or follow this link:\
   [Compliance policies - Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/#view/Microsoft_Intune_DeviceSettings/DevicesComplianceMenu/~/policies)
3. Click on **Create policy** and select **iOS/iPadOS** as Plattform and click on **Create**
4. Enter a Name for your Policy e.g. “Secure Contacts App Compliance Policy”
5. Set necessary *Compliance settings* and *Actions for noncompliance* depending on environment
6. Confirm each **Next**
7. In *Assignments* pane, click **Add group** and search for SCA-Testgroup & confirm **Select**
8. Click on **Next**
9. Click on **Create** in *Review + create* pane

<figure><img src="/files/HRv6MO095haJA71TjKPo" alt=""><figcaption></figcaption></figure>

### Conditional Access Policy&#x20;

1. Go to Endpoint security → Conditional access or follow this link:\
   [Conditional Access - Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/#view/Microsoft_AAD_IAM/ConditionalAccessBlade/~/Policies)
2. Click on **New policy** to create a new Conditional Access policy
3. Enter a Name for the Policy e.g. “Secure Contacts Conditional Access Policy”
4. Go to ***Users or workload identities*** in *Assignments*
5. *Include* your SCA-Testgroup to **Users and Groups**\
   \
   ![](/files/D6jgBTB23SG4C9gOYeQk)<br>
6. Go to ***Cloud apps or actions*** in *Assignments*
7. *Include as Cloud Apps the apps* **Office 365** and **Provectus - Secure Contacts**\
   \
   ![](/files/CSFWdZiWBE6Fwr5vjM4K)<br>
8. Set mandatory Conditions for your environment e.g. tick as a Condition for Client apps the value *Mobile apps and desktop clients*
9. Go to *Grant* in the *Access controls* pane
10. Set **Require compliant device**\
    \
    ![](/files/9OuFb6rnCpNIra3PKJq5)<br>
11. Set *Enable Policy* to **On**
12. Click on **Create**

{% hint style="info" %}
According to Microsoft, it is **mandatory** to target **Office 365** and **Secure Contacts** as Cloud App in your Conditional Access Policy in order to correctly implement SCA.\
It is required to add **Office 365** as Cloud App, because our Enterprise Application\
(Provectus - Secure Contacts) is using these data sources.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.secure-contacts.com/documentation/deployment-sca/deployment-for-your-devices-in-intune/deployment-ios-mdm-managed-and-complaint-device.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
