Learn how to deploy and configure AccessPoint in your Microsoft 365 and Azure environment
Last updated: March 29, 2026 by Steve
Getting Started with AccessPoint
Welcome to AccessPoint — the ATIP and FOI request management platform built for government organizations. AccessPoint runs entirely inside your Microsoft 365 and Azure tenant, giving you full control over your data with no external dependencies. This guide walks you through deployment, initial configuration, and adding your first users.
Prerequisites
Before you begin, ensure you have the following:
- Microsoft 365 subscription with access to SharePoint Online
- Azure subscription in your organization's tenant
- Admin permissions — SharePoint Admin or Global Admin for SPFx deployment; Azure Contributor or Owner for infrastructure provisioning
- Modern web browser — Edge, Chrome, Firefox, or Safari
AccessPoint has no direct dependencies on Microsoft 365 licensing tiers. It runs as a SharePoint Framework web part hosted on a SharePoint page or as a Microsoft Teams app, so any user with access to SharePoint or Teams can use it. No Power Platform or Dataverse licensing is required.
What Gets Deployed
AccessPoint consists of several components that are installed into your own tenant:
| Component | Where It Runs | Purpose |
|---|---|---|
| SPFx Web Part | SharePoint Online / Teams | User interface (TypeScript, React, Fluent UI) |
| ASP.NET Core 10 Web API | Azure App Service (Linux) | Business logic, data access, document processing |
| Azure SQL Database | Azure SQL | Relational data store (55 tables) |
| Azure Blob Storage | Azure Storage Account | Document file storage |
| Application Insights + Log Analytics | Azure subscription | Telemetry, diagnostics, alerting |
All data resides in your Azure tenant. The publisher (Realizer) has no runtime access to your data and no customer information is transmitted outside your environment.
Get Your Subscription
Before deploying, you need an active AccessPoint subscription (trial or paid). Get yours from Microsoft AppSource:
Deployment Overview
AccessPoint is deployed using a Bicep ARM template and a PowerShell deployment script that provisions all Azure infrastructure into your own subscription. The SPFx web part and Teams app are installed from Microsoft AppSource.
You can deploy by clicking the Deploy to Azure button (which pre-loads the ARM template in the Azure Portal) or by running the PowerShell script directly for full control over the process. Organizations with strict change control can review, customize, and integrate the templates into their existing deployment pipelines.
Full deployment instructions are in the Deployment Guide.
Initial Configuration
After deployment, configure AccessPoint for your jurisdiction by importing a configuration pack. Configuration packs pre-populate statutory deadlines, exemption and exclusion codes, workflow stages, and language settings for your legislative framework.
Available configuration packs:
- Canadian ATIP — Federal and Provincial
- US FOIA — Federal agencies
- EU GDPR — Data subject access requests
- UK FOI — Freedom of Information Act
- Australian FOI — Freedom of Information Act
To import a configuration pack:
- Open AccessPoint and navigate to Administration > Configuration
- Select Import Configuration Pack
- Choose your jurisdiction and confirm
Additional jurisdictions and custom configurations can be created by your administrator through the built-in settings. You can customize statutory deadlines, exemption codes, workflow stages, and language settings after import.
Add Users
AccessPoint leverages your existing Microsoft Entra ID accounts. Users sign in with their organizational credentials — no additional usernames or passwords to manage. Authentication is handled through OAuth 2.0/OIDC with JWT bearer tokens.
Assign users to roles to control what they can see and do:
| Role | Description |
|---|---|
| Administrator | Full system configuration and management |
| Subject Access Officer (SAO) | Manage requests, assign tasks, view all request details including requestor PII |
| Reviewer | Review documents and provide recommendations |
| Custodian | Respond to task assignments and upload documents (no access to requestor PII) |
| Contributor | Create and update content within assigned requests |
| Reader | Read-only access to assigned requests |
To add users:
- Navigate to Administration > Users
- Search for users by name or email (pulled from Entra ID)
- Assign one or more roles
Install the Teams App (Optional)
AccessPoint is available as a Microsoft Teams personal app and configurable tab. Installing the Teams app enables:
- Activity feed notifications with deep links back to specific requests
- Personal app access to AccessPoint without leaving Teams
- Tab integration for embedding AccessPoint in a Teams channel
To install:
- Go to the Teams Admin Center
- Upload the AccessPoint Teams app package
- Configure app setup policies to make it available to your users
Verify Your Setup
Once deployment and configuration are complete, open AccessPoint from SharePoint or Teams. You should see the main dashboard with your jurisdiction's configuration applied.
Next Steps
- User Guide — Learn how to create and manage access requests
- Admin Guide — Detailed administration and configuration instructions
- Technical Architecture — Architecture overview for IT teams and security reviewers