Microsoft 365 & SharePoint
Contract management on Microsoft 365 and SharePoint
SharePoint contract management means storing, routing and tracking contracts inside Microsoft 365 instead of in a separate system. CAMARC can run as a complete contract lifecycle platform on that stack. In the published Fortune 500 REIT deployment it uses SharePoint Online for documents, Power Automate for approvals, Power Apps for the interface, Azure OpenAI for the AI assistant and Power BI for reporting, all inside the client’s own Microsoft 365 tenant, under the identity and permissions it already manages.
- Runs inside the client’s own Microsoft 365 tenant
- Built by Al Rafay Consulting, a Microsoft Solutions Partner
- E-signature through Adobe Sign
- 500+ contracts a month in production
Can you manage contracts in SharePoint?
Yes, up to a point. SharePoint Online gives you document libraries, metadata columns, version history, permissions and search, which is enough to store contracts in one place. Many real estate teams start there.
What SharePoint does not give you out of the box is the contract process around those files: a request form for each contract type, routing to legal and risk review, generating the document from an approved template, sending it for signature, tracking renewal and insurance dates, and reporting on where every contract is. Teams that need those usually end up building them with Power Automate and Power Apps, one flow at a time.
CAMARC is that process already built and configured to your contract types and approval rules. In the published REIT deployment it runs on those same Microsoft 365 services.
Which Microsoft 365 services does the published deployment use?
The first five are the stack documented in the published life-science REIT deployment; contracts are executed through Adobe Sign.
SharePoint Online
Document management: every contract, version and attachment, with SharePoint permissions.
Power Automate
The workflow engine that moves contracts through request, review, execution and renewal.
Power Apps
The interface your team uses to request, review and track contracts.
Azure OpenAI
The AI layer behind clause suggestions and plain-language questions about your contracts.
Power BI
Dashboards for leadership, legal and operations.
Adobe Sign
Contract execution, started from inside CAMARC with signer order and deadlines.
Why run contract management inside your Microsoft 365 tenant?
- Contracts stay where your documents already are. No second document store to secure, back up and audit.
- Same identity and access. Users sign in with the accounts IT already manages, and access follows roles you control.
- Familiar for IT. The platform is made of Microsoft services your IT team already knows how to govern.
- Data you can reach. Contract data can feed Power BI and, as in the published deployment, your ERP.
In the published REIT deployment, the case study reports that the platform runs inside the client’s existing Microsoft 365 tenant with no additional platform licensing and no data egress. What applies to you depends on your Microsoft 365 plan, which we review during scoping.
Who builds and supports CAMARC?
CAMARC is built by Al Rafay Consulting (ARC), a Microsoft Solutions Partner that has spent more than a decade building Microsoft 365, SharePoint and Azure systems for property management companies, life-science real estate firms and investment groups. Al Rafay Consulting handles rollout, training and ongoing support.
Frequently Asked Questions
Is SharePoint a contract management system?
SharePoint is a document management platform. It can store contracts with metadata, versions and permissions, but it does not include request intake, approval routing, document generation, e-signature or renewal tracking unless you build them. In the published deployment, CAMARC adds those on top of SharePoint Online.
Do we need extra Microsoft licenses to run CAMARC?
It depends on your Microsoft 365 plan. In the published REIT deployment, the case study reports no additional platform licensing was required. We review your plan with you during scoping.
Does CAMARC send contract data outside our tenant?
In the published deployment, the case study reports the platform runs entirely inside the client’s Microsoft 365 tenant with no data egress, including the Azure OpenAI layer. We confirm the architecture for your environment during scoping.
Can we keep using Adobe Sign?
Yes. CAMARC uses Adobe Sign for execution: signers, signing order and deadlines are set in CAMARC and the signed document comes back to the contract record.
We already built contract flows in Power Automate. Do we start over?
Not necessarily. Existing flows, lists and libraries are reviewed during discovery so we can decide with you what to keep. Existing contracts are migrated during go-live.
See CAMARC running on Microsoft 365
We will show the SharePoint, Power Automate and Adobe Sign pieces working together on one of your contract types.