From this release on, you sign in to the Customer Portal and the Partner Portal with your Microsoft account. Your access now follows your Microsoft environment: anyone disabled there is out of Attic too. Also new are roles and permissions, marking an incident as handled without the proposed fix, and for partners their own API accounts, themes and creating end customers themselves.
Sign in with Microsoft
You sign in to your portal with the same Microsoft account you already work with, with the security your organisation already has in place there. If you already have an account with a password, link your Microsoft account in your profile or right when you sign in. Colleagues without an account sign up through Microsoft and become active after approval. Microsoft sign-in can be made mandatory per organisation.
Access follows your Microsoft environment
Your portal session is tied to your Microsoft sign-in. If an account is disabled in Microsoft or a session is revoked there, access to the portal ends too. When someone leaves, you switch them off in one place.
You see what you are allowed to
The portal only shows the sections and actions you have permission for.
Incident handled, without the fix
Sometimes you have already solved an incident your own way, or the proposed fix does not suit your situation. You can then mark the incident as handled and decline the proposed fix. Attic does not carry out that fix, and the check simply stays active.
Fixed
On some incident actions, the message "action not available" appeared incorrectly. This has been fixed.
What Attic MDR includes, from continuous hardening to 24/7 detection and response, is on Agentic MDR for Microsoft 365.
For partners
In the new Partner Portal you sign in with Microsoft. As an admin you connect your Entra tenant yourself, decide in Entra who has access and with which role, and can make Microsoft sign-in mandatory. How to set this up is described step by step in Enable SSO in the Attic Partner Portal. You view and revoke your team's sessions and tokens yourself. Integrations get a separate API account. You also create your own themes, create and delete end customers, and start a chat with Attic from within the portal.
Using the API? An API token of a regular user expires at that user's first Microsoft sign-in, and with mandatory Microsoft sign-in, API tokens only work through an API account. So move your integration to an API account first.
More on working with Attic as an MSP: Attic for MSPs.
Not a customer yet?
Try Attic MDR free for 14 days and see in your own portal how your Microsoft 365 environment is doing: start your trial.
Previous release: Attic Release Notes 2026.10.0.