Document the browser-based SharePoint sign-in and move superseded setup to a legacy page
The installer no longer uses an embedded Internet Explorer cookie login for
SharePoint; it opens the admin's default browser and signs in with OAuth. That
changes what admins need to prepare, so the deployment docs are updated to match.
Nothing has been deleted. Advice that no longer applies to current releases moves
to a new "Legacy SPO web setup" page: the old cookie login, the username/password
AITracker PowerShell scripts and their SecureString flow, the MFA workaround, and
the SharePoint Online Management Shell installer-machine prerequisite.
Updated pages:
* Prerequisites - deployment credentials now describe an interactive sign-in
rather than stored SharePoint passwords; installer machine needs a modern
browser rather than the SPO Management Shell; added the login.microsoftonline
.com and loopback network rules.
* Deployment Guidance - rewritten SharePoint tab section covering who needs to
sign in and why, and the optional own-app-registration fields.
* App Registrations Setup - states plainly that two registrations is the whole
list, since sign-in reuses an app Microsoft already publishes.
* Manual Install Web Tracking and Config - points at the installer first and
keeps only the PnP/on-premises scripts; the basic-auth walkthrough moves to
the legacy page.
* Troubleshooting - new section for sign-in failures (loopback blocked, consent
errors, AADSTS50194, access denied on the app catalog, slow app-catalog
propagation). The old MFA IdcrlException workaround moves to the legacy page,
as the browser sign-in supports MFA natively.
* Uninstall - use the installer's Remove AITracker button; the PowerShell is the
alternative.
* Release Notes - the sign-in change, and a Code maintenance line for the
dependency work.
The move also strips a real demo-tenant name and a real user address out of the
sample script output, replacing them with contoso placeholders.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 43dbb877-89bb-44dd-8d93-27a78f34c7ca
Add dedicated 'Runtime app reply URLs' page and link from setup
Move the runtime app reply URL / redirect URI guidance out of the App
Registrations Setup page into a focused page. Consolidate the duplicate
'Add Platform configurations' and 'Enable Implicit Grant Flow' sections,
document the exact HTTPS-root-with-trailing-slash reply URL, the ID-tokens
requirement for the hybrid code id_token flow, multiple environments and
AADSTS50011 troubleshooting. Keep the original heading/anchor and link to
the new page from the setup page, sidebar and manual-install page.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Wiki: finish branding modernisation + fix two malformed Analytics tables
- Modernise generic 'Office 365' platform references to 'Microsoft 365' across
the wiki (44 occurrences), now that the product is 'Microsoft 365 Advanced
Analytics'. The real 'Office 365 Management [Activity] API' name and code
identifiers (Office365ActivityImporter, o365_client_applications) are preserved.
- Analytics - Data model: fix the malformed 'Usage metrics' table (the header had
two columns but the data row had four; the stray cells duplicated the
App-per-platform table below).
- Analytics: de-indent the Runbooks table so it renders reliably (it was indented
under a list item).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Wiki: modernise product name to 'Microsoft 365 Advanced Analytics' + accuracy/structure polish
- Standardise the product name to Microsoft 365 Advanced Analytics (was a mix of
'Office 365 Advanced Analytics [Engine]', 'M365 Advanced Analytics', 'O365...').
Code identifiers (Office365ActivityImporter), the Office 365 Management Activity
API name and the literal 'O365 Adv Analytics Setup Rule' firewall rule are
deliberately preserved.
- Replace legacy docs.microsoft.com links with learn.microsoft.com.
- Tie the monitoring trio together: Health Alerts and Monitoring now cross-link
Monitoring system performance and vice-versa.
- Verify: fix informal wording and add a 'What good looks like' pass/fail checklist.
- Troubleshooting: point fatal-exception reports at GitHub Issues (with a
redact-secrets warning) instead of an unaddressed 'please email'.
- Manual setup: clarify the importer uses the App Insights connection string, with
the instrumentation key still needed for AITracker/legacy logging.
- Architecture & costs: document the basis for the ~EUR170/month estimate.
- CSP page: add deployment/context cross-links.
- Align the Analytics page title with the sidebar ('Activity & Usage Analytics').
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Wiki: split app-registration setup out of Deployment Guidance into its own page; update links + sidebar
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>