> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/stonly-import-secure-defender/defender-policies.md).

# Defender Policies

Augmentt integrates with Microsoft Defender and allows you to configure key email security policies directly from the platform. These policies help strengthen your organization's security posture by applying recommended protections across supported tenants.

From the **Secure > Defender > Policies** section, you can deploy and manage the following policy types:

* Anti-phishing
* Anti-spam
* Anti-malware
* Safe Attachments
* Safe Links

Augmentt provides default policy configurations based on security best practices. These configurations can be deployed to help quickly establish baseline protections while reducing the need for manual configuration in Microsoft Defender.

Policies can be applied and managed across your tenants to ensure consistent protection against common email threats such as phishing, spam, malware, and malicious links or attachments.

## How Augmentt reports Defender posture

Augmentt's Defender security recommendations are sourced from the Microsoft Secure Score. Microsoft indicates that a 24–72 hour delay is to be expected for the Secure Score to reflect changes made to the tenant's posture.

Anti-phishing, Safe Attachments and Safe Links are features of Microsoft Defender for Office 365 and require additional licensing. These protections are not included with standard Microsoft 365 or Office 365 E3 licenses alone.

To use these features, one of the following licenses is required:

* Microsoft Defender for Office 365 Plan 1 (add-on for Microsoft 365 / Office 365 E3)
* Microsoft Defender for Office 365 Plan 2 (included in Microsoft 365 E5 or E5 Security)
* Microsoft 365 Business Premium (includes Defender for Office 365 Plan 1)

If the required licensing is not present, Safe Attachments and Safe Links policies cannot be deployed or enforced.

## Deploying Defender policies

Augmentt allows administrators to deploy Microsoft Defender policies using either Policy Templates or Baselines.

* **Policy Templates** deploy a single Defender policy configuration.
* **Baselines** deploy a predefined group of Defender policies designed to provide a recommended security starting point.

To deploy a Defender policy:

1. Navigate to **Secure > Defender > Policies**.
2. Select the tenant where the policy will be deployed.
3. In the upper-right corner of the dashboard, click **Create New**.
4. Choose **Baseline** or **Policy** and click **Next**.
5. Configure the deployment settings for the selected policy or baseline.
6. Click **Next** to proceed to the policy review page.
7. Review the policy configuration and deployment details.
8. Click **Deploy Policy** to apply the configuration.

Administrators can choose to deploy individual policies or baselines depending on their security preference and requirements.

## Creating templates and baselines

With the Augmentt Defender module you can create and manage Defender policy templates and baselines, allowing you to consistently deploy security policies across all your customers. This helps standardize security configurations and simplifies the onboarding of new tenants.

Using this feature, you can:

* Import your existing Microsoft Defender policies or use Augmentt out-of-box policy templates
* Create baselines that align with your organization's security strategy
* Deploy policies or baselines consistently across multiple tenants

### Creating templates

Templates are exported Defender policies that can be reused and deployed across tenants through Augmentt. To get started, first create or configure your policies in a connected Microsoft environment.

1. Navigate to **Secure > Defender > Templates**.
2. Click **Create New > Template**.
3. Select the tenant and the policy type.
4. Select the existing Defender policy you want to import.
5. Name your template.
6. Add a description if needed.
7. Click **Create**.

The policy template is now stored in Augmentt and can be reused when deploying policies to other tenants. Repeat this process to import all Defender policies you want available for deployment.

### Creating baselines

Baselines are a collection of Defender policy templates that can be deployed together across tenants. They help ensure consistency and reduce configuration errors by deploying a predefined set of security policies.

1. Navigate to **Secure > Defender > Templates**.
2. Click **Create New > Baseline**.
3. Select the policy templates you want to include in the baseline.
4. Name your baseline.
5. Click **Create**.

Your baseline is now stored in Augmentt. You can create multiple baselines to support different security strategies or customer environments.

## Troubleshooting deployments and posture

If a Defender policy deployment fails, a recommendation sits as Partially Compliant after you've made the change in the tenant, or a check shows as Not Measured, walk through the dedicated troubleshooter: **Troubleshooting Defender Policy Deployment and Compliance**.

It covers the three most common states side by side (Forbidden / Partially Compliant / Not Measured), the license matrix for the checks that require specific Defender plans, and an escalation checklist if Augmentt Support needs to get involved.


---

# 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://helpdesk.augmentt.com/stonly-import-secure-defender/defender-policies.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.
