Get started

If you’re evaluating AutoTag for governance Phase 1: in development

Governance evaluations start with a discovery call, not a Bot deployment. We’ll walk through your tenant, your label catalogue, and your Purview rollout. Then we’ll discuss whether AutoTag fits. If so, we’ll scope a Phase 1 design-partner engagement.

Book a governance discovery call

AutoTag is licensed to a Microsoft 365 tenancy and deployed directly inside it. JFDI Consulting Ltd does not gain access to your data at any point. Every action AutoTag takes happens within the boundary of your own tenant.

Three steps to automatic tagging

Talk to us

We discuss your tenancy, your existing taxonomy, and the libraries you want tagged.

Deploy a Bot

We deploy AutoTag inside your Microsoft 365 tenancy. Your data never leaves it.

Tag your data

Your Bot reads your taxonomy and applies tags across the libraries you choose.

The first 30 days are on us

We let you test drive AutoTag against your own SharePoint-hosted files for 30 days, free of charge. That means a real Bot deployed in your real tenancy, reading your real taxonomy, applying tags to libraries you nominate. No simulation, no sandbox: the production product, configured for your environment.

At the end of the trial you keep what AutoTag has tagged. If you decide to subscribe, the Bot stays deployed and continues working. If you decide not to, the metadata it applied stays on your items. There is nothing for AutoTag to “take back”.

  • Compatible with SharePoint Online and SharePoint Server (Subscription Edition, 2019, 2016, 2013)
  • All SharePoint column types are supported
  • Works with any file format: AutoTag applies metadata without touching the target content
  • No file count limits: process as much content as you have
  • AI-assisted tag suggestions based on document topics and themes

What happens during a Bot deployment

A single AutoTag Bot is configured against a source list (your taxonomy) and one or more target lists or libraries (the content you want tagged). Source and target can be selected by URL, by site collection search, by content type name or ID, or via a wild card pattern across the tenancy. From there the Bot reads, cross-references, and applies the missing metadata.

Each Bot runs continuously once deployed. New documents arriving in target libraries are tagged on arrival. Backfill jobs sweep historical content. Edits trigger re-evaluation. The metadata layer becomes self-maintaining.

Ready to put metadata on autopilot?

Talk to JFDI about deploying AutoTag in your tenancy.

Get in touch