v0.6.98: Exchange Online, Teams and SharePoint tests, and Maester 2.3
Managed runs connect to Exchange Online, Security & Compliance, Teams and SharePoint Online with no new secret or certificate, and move to Maester 2.3. New tests are reviewed in bulk, and the portal is much faster.
What’s new
- Exchange Online, Teams and SharePoint tests in managed runs. Each tenant has a Connect services button once its Microsoft Graph connection is verified. Choose Exchange Online (which includes Security & Compliance), Microsoft Teams and SharePoint Online, grant access, then verify each service. Once a service verifies, the next run includes its tests. Exchange Online can take a while to honour a newly assigned role, and until it does a run reports that it couldn’t reach Exchange and skips those tests. Tests for a service you haven’t connected are skipped, as before.
- No new secret or certificate. The services use the credential your runner app already has. Connecting adds permissions and read-only directory roles to the app:
Exchange.ManageAsAppand Global Reader for Exchange Online, Teams Reader for Teams, andSites.FullControl.Allfor SharePoint Online. SharePoint is unticked by default and asks you to confirm, because Microsoft offers no smaller permission for reading tenant settings. - Grant access in the setup app. One sign-in at setup.maester.cloud grants everything you ticked, for any tenant you assess. If you aren’t an administrator of the tenant, the portal and the setup app give you a script to hand to someone who is. The portal’s own sign-in is not asked for any new permission.
- Remove a service connection. Each service has Remove. Runs stop using the service and its tests are skipped. The permission and role stay on your runner app until you remove them in Microsoft Entra, and the confirmation names them.
- Maester 2.3. Managed runs use Maester 2.3, up from 2.1. It adds 287 tests, 258 of them for Active Directory, and SharePoint grows from 2 tests to 14. Read “Before you update” below.
- Review new tests by product and feature. The New tests page groups tests by product and, in a long group, by feature. Each group has its own Skip and Include. Filter by product, severity or text, select everything that matches, and decide in one go. A decided test leaves the list with an Undo notice, and recent decisions stay at the foot of the page for 90 days. The Tests page now lists new tests that have no results yet, so a skipped test can be found and turned back on.
- A much faster portal. List and summary pages no longer download every test’s result text. In our test with 10 tenants and 10 runs each, the Tests page went from 55 seconds to under 2, and Overview from 6 seconds to 1. Result text still shows on the test’s page.
- Open what you click. A row on Runs opens the run, with icon buttons for the raw report and the changes since the previous run. A row on Changes opens the test. Products on Overview and Changes open the Tests list filtered to that product.
- Accept a risk in place. Accept risk on a test’s page opens the form over the page, and the decision shows there after you save.
- The managed runner on Access. The Access page shows the identity your managed runs use, with a link to it in Microsoft Entra. Add or remove users in Entra opens your portal’s enterprise application on Users and groups. The default user role has moved to a Settings card on the same page, with guidance on which value to pick.
- Times on your own clock. Schedule windows and the daily summary time are shown and entered in your own time zone. The time zone settings have been removed. Existing schedules keep running at the same times.
maester.fyiis the default domain for an instance’s included subdomain.- Copy a setup guide. The manual guides in setup (the sign-in app, the shared mailbox and running setup from PowerShell) are wider and easier to follow, and Copy puts a guide on the clipboard with formatting or as Markdown, with your instance’s values filled in. Use it to hand a step to the administrator who has to do it.
Fixes
- Report emails: two instances in the same Microsoft 365 tenant no longer take the mail permission from each other. Each instance now has its own Exchange Online scope. If you run one instance, nothing changes.
- Settings now says when Exchange Online is refusing your report emails, with the reason.
- In setup, the Email step waits and retries on its own after you first approve Exchange Online access. Before, it failed until you signed out and back in.
- If you registered the portal sign-in app by hand with Configure manually, the portal could refuse you with “access validation failed (401)”, because an app registered in the Microsoft Entra admin center issues version 1 tokens by default. The manual steps now include setting the access token version to
2, and the portal’s error names this cause and the fix. Setup’s automatic path was never affected. - In setup, signing in to grant service access returns you to Tenants when your Azure sign-in has expired, and the grant goes ahead.
- An Update keeps your instance’s account ID. Before, an update from PowerShell or with a typed access code cleared it.
- An instance deployed from
Start-MaesterCloudSetup -DisableTelemetrynow gets a working support widget. - Setup from PowerShell can check a new subdomain on any of the offered domains, not only the default one.
Before you update
- Five new read-only Microsoft Graph permissions. Some Maester 2.3 tests need
AuditLog.Read.All,EntitlementManagement.Read.All,NetworkAccess.Read.All,RoleEligibilitySchedule.Read.DirectoryorRoleManagementAlert.Read.Directory. Until your runner app has them, those tests are skipped. They don’t fail. Updating to v0.6.98 doesn’t add them. Grant them in each tenant with step 4 below. - SharePoint tests need the SharePoint connection. Maester 2.3 reads SharePoint settings through SharePoint, not Microsoft Graph. Until you connect SharePoint Online, all 14 SharePoint tests are skipped, including the two that ran before.
- Active Directory tests can’t run in a managed run, because a managed run can’t reach a domain controller. If you hold new tests for review, you can skip the whole Active Directory group at once on the New tests page.
- A run uses more compute when a service is connected. A run for a tenant with Exchange Online, Teams or SharePoint connected uses 2 vCPU and 4 GiB of memory while it runs. Other runs stay at 1 vCPU and 2 GiB.
- The daily heartbeat carries six more values: your report email cadence, and counts of report recipients, portal users, accepted risks and turned-off tests, plus whether a custom domain is set. They are counts, yes/no values and the cadence (off, per run or daily), with no names, addresses or domains.
How to update
- Open setup.maester.cloud and sign in with the account you used for setup.
- Choose your instance and select Update to v0.6.98. The update applies in place, and your stored results and history are untouched.
- To run the Exchange Online, Teams and SharePoint tests, open Tenants and select Connect services for each tenant.
- To grant the five new Microsoft Graph permissions, open Tenants in your portal and choose a tenant. On its Microsoft Graph connection, select Details, then the Setup tab, and give the PowerShell script to an administrator of that tenant (a Global Administrator or Privileged Role Administrator). They run it in PowerShell 7 with the
Microsoft.Graph.Authenticationmodule. Then select Verify. The script only adds what’s missing, so it’s safe to run again. Use the script, not the admin consent link on the same tab, which only grants the permissions your runner app had when it was created. Repeat for each tenant.
If you run setup from PowerShell, update the module first with Update-Module MaesterCloud, then run Start-MaesterCloudSetup.