microsoft-365-docs
microsoft-365-docs copied to clipboard
MicrosoftDocs
Add SCCM Role Requirement
Added reference to the SCCM System Role: Endpoint Protection which is required for AV and ASR policies to be properly deployed to an endpoint.
Docs Build status updates of commit 0bd72cd:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md | :warning:Warning | Details |
microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md
- Line 36, Column 3: [Warning: hard-coded-locale - See documentation]
Link 'https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/endpoint-protection-site-role' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 36, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/endpoint-protection-site-role' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 17d9d01:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md | :warning:Warning | Details |
microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md
- Line 36, Column 3: [Warning: hard-coded-locale - See documentation]
Link 'https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/endpoint-protection-site-role' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 36, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/endpoint-protection-site-role' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 571f413:
:bulb: Validation status: suggestions
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md | :bulb:Suggestion | Details |
microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md
- Line 36, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-protection-site-role' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 6e2e210:
:bulb: Validation status: suggestions
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md | :bulb:Suggestion | Details |
microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md
- Line 37, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-protection-site-role' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 16234fe:
:warning: Validation status: warnings
This comment lists only the first 25 files in the pull request.
microsoft-365/compliance/communication-compliance-solution-overview.md
- Line 6, Column 10: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.prod': 'microsoft-365-enterprise'.
microsoft-365/lti/index.md
- Line 10, Column 10: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.prod': 'microsoft-365-enterprise'.
microsoft-365/security/defender-endpoint/api-release-notes.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/apis-intro.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/application-deployment-via-mecm.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/assign-portal-access.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-simulations.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction.md
- Line 18, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-implement.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-operationalize.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-plan.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-test.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-reference.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-report.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/auto-investigation-action-center.md
- Line 20, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/autoir-investigation-results.md
- Line 7, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/automated-investigations.md
- Line 6, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/automation-levels.md
- Line 6, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/azure-server-integration.md
- Line 18, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/basic-permissions.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/batch-update-alerts.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/behavioral-blocking-containment.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/cancel-machine-action.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/check-sensor-status.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request. For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 0a09eb3:
:warning: Validation status: warnings
This comment lists only the first 25 files in the pull request.
microsoft-365/compliance/communication-compliance-solution-overview.md
- Line 6, Column 10: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.prod': 'microsoft-365-enterprise'.
microsoft-365/lti/index.md
- Line 10, Column 10: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.prod': 'microsoft-365-enterprise'.
microsoft-365/security/defender-endpoint/api-release-notes.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/apis-intro.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/application-deployment-via-mecm.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/assign-portal-access.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-simulations.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction.md
- Line 18, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-implement.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-operationalize.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-plan.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-deployment-test.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-reference.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-report.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/auto-investigation-action-center.md
- Line 20, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/autoir-investigation-results.md
- Line 7, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/automated-investigations.md
- Line 6, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/automation-levels.md
- Line 6, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/azure-server-integration.md
- Line 18, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/basic-permissions.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/batch-update-alerts.md
- Line 16, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/behavioral-blocking-containment.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/cancel-machine-action.md
- Line 19, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
microsoft-365/security/defender-endpoint/check-sensor-status.md
- Line 17, Column 16: [Warning: ms-prod-technology-invalid - See documentation]
Invalid value for 'ms.technology': 'mde' is not valid with 'ms.prod' value 'm365-security'.
This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request. For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit 6a498bc:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Learn Build status updates of commit 1d3e39f:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/security/defender-endpoint/configure-endpoints-sccm.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel