Reviewing a SaaS integration
Check the permissions, data flows and failure behaviour of a new SaaS integration. Run a limited pilot and test how to disconnect it.

A new integration can move customer details between your sales system and accounting software, publish a document or send messages on someone’s behalf. Before connecting it, check the access behind the feature.
The supplier-risk guide covers the wider relationship. An integration review needs to examine the particular connection you’re about to switch on, even when the supplier is already trusted.
Start with the job and the data flow
Write down the task, the business owner and the systems involved. Identify what the integration reads, changes, deletes or sends. Include attachments, logs, error messages and any data copied into the supplier’s service.
Ask where processing occurs, how long copies are retained and which subcontractors receive them. Check whether the connection is one-way or can write changes back into your primary records.
For example, a contact-sync tool may only need a limited customer list. It shouldn’t receive payment authority merely because the same accounting API offers that permission.
Review permissions before granting consent
OAuth can let an application connect without receiving your account password. It doesn’t tell you whether the app needs all the access it’s asking for.
Microsoft’s consent guidance explains how users and administrators approve application access. Review each requested permission, the publisher and the application ID. A familiar product name on a consent screen isn’t enough.
Distinguish delegated access, which operates for a signed-in user, from application permissions that can operate without one. Microsoft’s permissions overview describes that difference. Confirm resource restrictions and avoid granting organization-wide access when a narrower supported scope meets the need.
Record consent centrally, including the administrator or user who granted it. Decide who signs off if it later asks for more permissions. Don’t use a shared administrator login as the integration’s permanent connection.
Check evidence and contractual responsibilities
Request security evidence relevant to this service and the data it will handle. If a supplier provides an assurance report, such as a SOC 2 Type II report, check its period, scope, exceptions and responsibilities left to your organization. The report won’t tell you whether this connector is set up safely.
Review confidentiality, incident notification, retention, deletion, support access and subcontracting terms. Agree how you’ll receive changes to permissions or data handling. A general claim of compliance won’t answer questions about how you’ll use it.
For organizations subject to PIPEDA, the Privacy Commissioner’s cross-border processing guidance explains ongoing accountability for transferred personal information. Canadian hosting alone doesn’t settle that responsibility. Provincial, public-sector and client requirements need their own review: in Quebec, for example, a business must assess privacy factors before personal information is communicated outside the province.
Pilot normal work and failures
Use made-up records, or a small set of real ones the business owner has agreed to. Confirm that only intended fields and records move. Test duplicates, partial failures, retry behaviour and a destination that’s temporarily unavailable.
Check whether a repeated request creates a second invoice or sends the same message twice. Decide which system’s value stands when they differ, and make sure an error reaches someone who can act on it.
Test the effect of changing the connection owner’s account or credentials. Assign an operational owner and a backup contact so a staff departure doesn’t leave a business process unattended.
Test disconnection before expanding access
Practise disabling the connector and checking that new reads and writes stop. Revoke the relevant permissions, tokens, credentials or webhooks through each system’s supported process. Deleting a user-facing app icon may leave its access in place.
Microsoft’s permission-update guidance notes that removing a requested permission from an app registration also requires revoking existing consent. Check application permissions separately from user sessions.
Confirm what data remains with the supplier, the export route and deletion arrangements, including backups and logs. The data-portability guide covers whether exported records can be used independently.
Roll it out more widely only once the owner has the permission record, pilot results and a working disconnect procedure. Talk to us if you need help reviewing or building a connection between your business systems.


