When scanning your tenant with BindTuning, it does more than report what it finds. It translates your governance data into a prioritized set of recommendations, each pointing to a specific action you can take to raise your Integrity Score and reduce risk across your Microsoft 365 environment.
Recommendations are organized in two ways: by integrity score category, which tells you what area of your environment is affected, and by type, which tells you what kind of action is needed. A third layer, severity, helps you prioritize what to tackle first.
Integrity Score categories
Every recommendation belongs to one of four integrity categories. These mirror the four dimensions used to calculate your Integrity Score, so you can always trace a recommendation back to the score area it affects.
Category | What it covers |
Adoption | How actively employees are using the intranet, communication tools, and content. Low adoption means key resources go unseen, alignment suffers, and the value of your M365 investment erodes quietly over time. |
Oversharing & access | Whether permissions, sharing links, and access levels match your security expectations. Oversharing increases exposure risk, while outdated or broken access can limit collaboration or leave sensitive content unprotected. |
Ownership | Whether every site, page, and key content area has a clear, active owner. Without ownership, workspaces go stale, content becomes outdated, and governance accountability disappears. |
Sprawl | Unnecessary sites, pages, content, or templates that accumulate over time. Sprawl increases maintenance burden, confuses users, and degrades the quality of information available to people and Copilot alike. |
To understand how these categories connect to your overall score, read Understanding the Integrity Score.
Recommendation types
Recommendations are also grouped by the type of action required. Understanding the type helps you plan your response, since some recommendations are about fixing what already broke, while others are about preventing the next problem before it starts.
Remediate
Actions focused on fixing issues that already exist in your environment. These are the most immediate recommendations, targeting risks or gaps that are already affecting your score. Examples:
Reviewing workspaces without sensitivity labels and applying the appropriate label to protect content.
Removing unnecessary sharing links that allow unrestricted access to files or sites.
Prevent
Actions designed to stop issues from occurring in the future by putting proactive controls in place. These close the door on problems that would otherwise reappear after remediation. Examples:
Publishing templates that ensure new workspaces are created with sensitivity labels and secure sharing settings by default.
Blocking the creation of "Anyone" sharing links across new sites.
Improve
Actions that enhance how your environment works, even when there is no immediate risk. These optimize processes, configurations, or user experiences that are functional but not yet at their best. Examples:
Deploying templates that transform underused spaces into valuable, organized destinations.
Configure
Actions related to setting up, customizing, or managing settings, templates, or policies to align with your organizational requirements and governance standards. Examples:
Configuring default storage limits and alerts for new sites.
Setting up a lifecycle management policy to define what happens when workspaces become inactive.
Recommendation severity
Each recommendation carries a severity level that reflects how significantly the underlying issue affects your Integrity Score. Severity helps you focus on what matters most, especially when you have multiple recommendations to work through.
Severity | What it means |
Critical | The issue is causing significant damage to your score and represents a serious governance or security gap. Address these first. |
High | The issue has a meaningful impact on your score and should be addressed soon. Leaving these unresolved will compound over time. |
Medium | The issue contributes to score degradation but poses a lower immediate risk. Resolving these improves overall hygiene and prevents future drift. |
Acting on recommendations
Recommendations surface directly inside the Integrity Score view. Each one includes a description of the issue, the category it belongs to, its severity, and a direct path to the action or setting that resolves it.
Some recommendations take you to a Pulse365 report where you can review affected workspaces and take action in bulk. Others point to Automate365, where you can publish a template or configure a policy that prevents the issue from recurring.
Fixing existing issues raises your score today. Preventing new ones keeps it there. The most effective approach combines remediation in Pulse365 with governance at creation through Automate365.
Your score updates with each rescan, so every action you take is reflected in a clear feedback loop between the work you do and the health of your environment.