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: stage the manual install, nest monitoring, flesh out cert auth/product notes
Manual installation (447-line page) split into an overview/index plus three
ordered stage pages so each phase is digestible and navigable:
- Manual Install Azure Resources (storage, App Insights, App Service, SQL,
Redis, Service Bus, Cognitive)
- Manual Install Deploy Binaries (publish web-jobs/website, app settings)
- Manual Install Web Tracking and Config (AITracker, SPFx extension, reply
URLs, filtered URLs)
The parent keeps its filename so inbound links still resolve; each stage has
prev/next navigation; in-page section references became cross-page links; the
Uninstall deep link to #deploy-aitracker-via-powershell was repointed.
Sidebar: nest the three manual-install stages under Manual installation, and
nest Health alerts + System performance under Monitoring.
Certificate authentication: add intro, a How it works summary (Key Vault, the
required O365AdvancedAnalytics CN, the UseClientCertificate setting) and a
Prerequisites section; tidy the verify-logs heading.
Product notes: clearer intro and cross-links (anchors preserved for inbound
links from Configuration reference and Troubleshooting).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>