This article is for Microsoft 365 administrators and future AODocs super administrators. It gives you the full path to set up AODocs for an organization that uses Microsoft 365 and doesn't use Google Workspace, from the creation of your AODocs domain to your first library and your first users.
You don't need a Google Workspace domain or a Google Account to use AODocs. Your users can sign in with their Microsoft account, and your attached files can be stored on a Microsoft platform such as SharePoint Embedded or Azure Blob Storage.
Note: If you use Google Workspace, follow Install AODocs instead.
Automatically generated table of contents
Before you start
Make sure you have:
- an AODocs subscription or trial for your organization – contact your AODocs sales representative or send an email to sales@aodocs.com
- the name of the email domain your users will sign in with, for example yourcompany.com
- the person who will be the first AODocs administrator (the domain owner), with an email address on that domain
- a Microsoft 365 administrator who will link your tenant to AODocs, with one of these Microsoft Entra roles: Global Administrator, Privileged Role Administrator, Cloud Application Administrator, or Application Administrator
- your Microsoft tenant ID – you'll need it for several steps. Learn how to find it in the Microsoft documentation: How to find your tenant ID
- a choice of AODocs instance (US or EU) – learn more: What are AODocs instances?
Who does what
| Role | Main tasks |
| Microsoft 365 administrator | Grants admin consent to the AODocs applications on your tenant, sets up Microsoft storage (SharePoint Embedded billing or Azure containers), deploys the Outlook add-in. |
| Domain owner (first AODocs super administrator) | Signs in first, adds other super administrators and library creators, creates the first libraries. |
| AODocs Support | Creates your AODocs domain with the sign-in methods and storage platforms you choose, links your Microsoft tenant, configures SAML sign-in if you use it, and activates the options of your subscription. |
Set up AODocs step by step
Step 1: Get your AODocs domain created
AODocs creates your domain for you. You choose the sign-in methods your users will see and the storage platforms your libraries can use.
Learn more: Get your AODocs domain ready without Google Workspace
Step 2: Authorize AODocs on your Microsoft tenant
Contact AODocs Support to link your Microsoft tenant to your AODocs domain. Send your Microsoft tenant ID and the email address of your Microsoft 365 administrator. Linking the tenant also turns on the synchronization of your Microsoft users and groups.
Your Microsoft 365 administrator then grants admin consent to the AODocs applications you use, and accepts the permissions requested by AODocs at consent:
| You want to | Article |
| Let users sign in with Microsoft on a tenant that restricts access to SaaS applications | Authorize AODocs on a Microsoft tenant |
| Use Microsoft groups in permissions, Migrate for AODocs, Bulk Updater, or the OneDrive picker | Enable Microsoft groups and AODocs products on your AODocs tenant |
| Store attached files in SharePoint Embedded | Understand and set up Microsoft SharePoint Embedded storage in AODocs |
| Store attached files in Azure Blob Storage | Set up Azure Blob Storage for AODocs |
Step 3: Sign in for the first time
- The domain owner opens the AODocs link for your instance, for example https://eu.aodocs.app/?aodocs-domain=yourcompany.com.
- The sign-in page shows only the sign-in methods selected for your domain. Click Sign in with Microsoft.
- The domain owner sees the AODocs homepage and has access to the tenant administration as super administrator.
Learn more: Sign in to AODocs
Step 4: Choose your storage platforms
On a domain without Google Workspace, libraries store their attached files on object storage – Google Drive isn't available. There's no single recommended platform: choose the one that fits your needs. You can use several storage platforms on the same domain: you select the storage platform of each library when you create it, and you can't change it afterwards.
| Storage platform | Where your files are | What you set up | Good to know |
| Microsoft SharePoint Embedded | In dedicated containers inside your own Microsoft 365 tenant, following your Microsoft 365 data residency | Admin consent to the AODocs application, and SharePoint Embedded pay-as-you-go billing linked to an Azure subscription – a Billing Administrator or Global Administrator of your tenant sets up billing (see Microsoft: Choose a billing model). AODocs creates and manages one container per library. When you create the library, select SharePoint Embedded in Storage type and enter your Tenant ID. | Separate from your SharePoint site quotas. Billed by Microsoft directly to your tenant, based on usage, such as storage, API transactions and egress. Importing files from OneDrive isn’t available yet. Learn more: Understand and set up Microsoft SharePoint Embedded storage in AODocs |
| Azure Blob Storage | In Azure containers, in the data center you choose | You create and manage the Azure storage accounts and containers. One container can store the files of one or more libraries. | Users can import files from OneDrive. Learn more: Set up Azure Blob Storage for AODocs |
| Amazon S3 | In S3 buckets, in the AWS Region you choose | You create and register the S3 bucket and set up AWS account trust. | Not supported by Migrate for AODocs, as a source or a destination. Learn more: Set up AWS account trust for Amazon S3 storage in AODocs |
| Google Cloud Storage | In your own buckets, in the data center you choose | You create and manage the bucket. | Users can import files from OneDrive. Learn more: Set up Google Cloud Storage for AODocs |
| AODocs Managed Cloud | In AODocs’ own Google Cloud Storage, in Google data centers in the European Union and the United States | Nothing: AODocs creates one bucket per document class automatically. | Users can import files from OneDrive. |
Learn more: What are the differences between the various storage platforms for AODocs?
Step 5: Add administrators and library creators
The domain owner is the only super administrator when the domain is created. Super administrators aren't synchronized from your Microsoft directory: add them manually.
Step 6: Create your first library
On a domain without Google Workspace, you can create Document Management libraries only. Team Folders and Secured Folders require Google Drive.
Learn more: Create a library from scratch and Create your first Document Management library
Step 7: Edit Microsoft Office files online
In libraries using SharePoint Embedded, Azure Blob Storage, Amazon S3, Google Cloud Storage or AODocs Managed Cloud, attached Word, Excel and PowerPoint files open automatically in the Microsoft 365 online editors. There's nothing to activate. Users open files in edit mode or view mode, depending on their rights on the document.
Learn more: Edit attached Microsoft Office files in libraries using Google Cloud or Azure Blob Storage
Important: To edit files with the Microsoft 365 online editors, users need a Microsoft 365 license. This license is often already included in standard Microsoft 365 plans.
Step 8: Deploy the Outlook add-in
Step 9: Invite your users
Share your AODocs link with your users and give them access to your libraries. You can use Microsoft groups in AODocs permissions.
For questions about licenses, contact AODocs Support or your AODocs sales representative.
Step 10: Migrate your existing content (optional)
To bring your existing content into AODocs, use Migrate for AODocs. Microsoft sources include OneDrive (directly or from a CSV file), Excel Online and Azure Blob Storage.
The migrated files are stored on the storage platform of the target library: SharePoint Embedded, Azure Blob Storage, Google Cloud Storage (including AODocs Managed Cloud) or Google Drive. Amazon S3 isn't supported, as a source or as a destination.
Note: To migrate to libraries using SharePoint Embedded, contact AODocs Support to activate this destination on your domain. Until then, Migrate for AODocs shows the message SharePoint Embedded destinations are temporarily unavailable.
Checklist
- Your AODocs domain is created with Microsoft sign-in and at least one storage platform.
- Your Microsoft 365 administrator has granted the admin consents you need.
- The domain owner can sign in and sees the tenant administration.
- Your storage platform is set up (SharePoint Embedded billing or Azure containers, if used).
- Other super administrators and library creators are added.
- Your first Document Management library is created.