Bauer Automate product roadmap
See what works today in ProjectPoint, Governance Suite and On Brand, and what we are working on next. PeoplePoint and DocuPoint are coming soon.
This shows direction, not delivery dates. Customer input gets priority consideration and visibility, never a delivery date. Plans can change as we learn.
Filter by product
Pick one or more products. Pick again to clear.
This shows direction, not delivery dates. Open an item to read more.
We add items here once our product backlog is prioritized. Until then, the feature lists below show what is available now and what is coming soon.
Nothing here yet.
Nothing here yet.
Nothing here yet.
Features of coming soon products, PeoplePoint and DocuPoint, show in the feature tables below.
A button creates one SharePoint site for each client, ready for that client's projects.
Your project manager runs it from a button on the client's record, so nobody builds a site by hand. If that client already has a site, ProjectPoint uses it and does not make a second one. The site also holds a list of that client's projects, and each new project gets its own Teams channel in the client's team.
A button adds a Teams channel for each new project in its client's team and adds the project team as members.
Start it from the project's record. If the client has no site yet, ProjectPoint creates it first. The team talks in the channel, files shared there are kept in the client's site, and an email confirms when the channel is ready.
New client sites join your SharePoint hub, which needs only the hub owner's permissions once a SharePoint admin has registered the hub.
A SharePoint admin registers your hub one time, before the first client site is made. After that, each new client site joins the hub as it is created, and the hub owner's permissions are all it takes. Your client sites then sit together under one hub.
Provisioning runs on the site owner's own permissions, with no tenant-wide app consent and no elevated role needed to run it.
ProjectPoint works through connections that belong to the site owner who installs it. It does only what that owner can already do in SharePoint, so running a provisioning needs no tenant-wide app consent and no elevated role. Your own settings still apply, such as who may create sites, and a SharePoint admin registers your hub once.
One list keeps every project with its client and a link to its Teams channel.
Every project is one entry in a single list in your own Microsoft 365. Each entry names the client and links to the project's Teams channel. The same button that makes the channel adds the link, so nobody has to paste it in.
Team members log time against a project and a category, with save and new for quick entry.
Pick the project and the category, add your time, and save. Save and new opens a blank form so you can enter several in a row, and you can reopen a saved entry to correct it. The entries stay in your own Microsoft 365.
A browser extension for Chrome and Edge logs time with start and stop timers and shows your day and week against budget.
The timer sits in the browser side panel, so it is there on whatever tab you are working in, and you can type notes while the work is on screen. When several timers run at once, the time is split evenly, so your total always matches the real time that passed. Your week view marks any workday with nothing logged, and the month view says whether you are on pace.
Project managers get a weekly email that sums up the time logged on their projects.
The email adds up the hours your team logged, and the numbers are in the email itself, so a project manager can read the week without opening a report. It is sent without anyone building it by hand.
Daily and weekly emails show hours logged against budget, and the weekly email adds an AI-written progress summary.
The daily and weekly emails show who logged what and which projects are on track against budget. The weekly email also carries a plain-English summary that AI writes from the time entries. The answer is in the email, so managers can see where each project stands without logging in and clicking through screens.
Admins view and edit every environment variable from one app, without opening each flow or app.
An environment variable is a saved setting that apps and flows can read. The fonts and colours in the Suite's branding kit are stored this way, and this app lists them alongside all your other environment variables. Your admin can change any of them in one place.
New canvas apps start with your fonts and colours already applied to classic controls.
Makers who start from the template do not have to set fonts and colours by hand, so new apps look like they belong to your company. The template reads its fonts and colours from settings stored in your own environment. Apps you built before are not changed by it, and applying your branding to them is separate work.
The app template shows your logo and loading spinner from files on the web or in SharePoint.
The spinner is the moving image people see while an app loads. Your logo and spinner files can sit on a public web page or stay private in SharePoint, and the template picks them up from there. Making a new custom spinner is separate creative work.
Fonts and colours come from environment variables, so a rebrand takes a few clicks and no app republishing.
Every font and colour in the canvas app template is read from an environment variable, which is a saved setting. To rebrand, your admin changes those settings and apps built from the template follow, so no one has to republish each app. Apps built another way are not covered, and applying your branding to them is separate work.
One central theme file sets the colours of your model-driven apps.
A model-driven app is a kind of Power Apps app that is built around your business data. You keep your brand colours in one theme file, and your model-driven apps take their colours from it, so a colour change is made once and not app by app.
When someone creates a canvas or model-driven app, the maker and your helpdesk get an email.
The email goes out when the app is created, so your helpdesk hears about it at the start and not only after something breaks or the maker has left. Who receives the alerts is set during setup. A maker can agree to stop getting these emails for a set number of days, and they start again by themselves.
When someone creates a Power Automate flow, an email alert goes out.
The email goes out when the flow is created, so someone in your organisation knows it exists from the start. That way a flow is not first noticed when it fails or when its maker has left. A maker can agree to stop getting these emails for a set number of days, and they start again by themselves.
Makers can agree to pause creation alerts for a set number of days, and the alerts turn back on by themselves.
A maker fills in a consent form. After that, the Suite stops sending that maker app and flow creation alerts until the pause ends, then starts again on its own. The pause applies to that maker only, and it always ends, so the alerts cannot stay off for good.
A sample flow shows how to send an email and Teams alert, with a link to the failed run, when any step fails.
The alert carries a link named after the flow, and the link opens the exact run that failed. Whoever gets the email or Teams message can start at the problem instead of searching for it. Because it is a sample flow, people who build flows can copy the same pattern into their own.
A daily check turns back on flows that Power Automate switched off for the most common reasons.
This keeps a flow that Power Automate switched off after a temporary failure from staying off without anyone noticing. The check runs by itself once a day. It uses a service identity, an account made for the job and limited to the actions it needs, not a personal account.
Only members of a chosen security group can make apps in the default environment, and a daily check keeps it that way.
By default, every licensed user can build in the default environment. Your admin picks the security group, and the Suite updates maker access whenever the group changes. A daily check covers the case where Microsoft resets the setting.
Your branded Word, PowerPoint, Excel and Outlook templates appear in the File > New gallery.
Word, PowerPoint and Excel carry a document theme that matches your brand.
A theme sets the colours and fonts that a document draws on. These themes are made from your brand and added to Word, PowerPoint and Excel. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
A new blank Word document opens already styled in your brand.
Word builds each new blank document from a default template file called Normal.dotm. On Brand replaces that file with a branded one, so a blank document already carries your brand. The deployment backs up the existing default before it replaces it. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
New emails in Outlook start from a branded default template.
The default template for new Outlook messages is a file called NormalEmail.dotm. On Brand replaces it with a branded one, and the deployment backs up the existing default first. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
A new blank Excel workbook starts from your branded default.
The default file that Excel uses for a blank workbook is called Book.xltx. On Brand replaces it with a branded one, so a new workbook starts on brand. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
A new PowerPoint deck starts from your branded default theme.
The default theme is what a blank presentation opens with. On Brand replaces it with your branded theme. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
The File > New gallery lists only your own branded templates.
Your templates live in one SharePoint library that syncs to each connected device, so a change usually reaches people in minutes.
You update your templates in one SharePoint library. OneDrive syncs it to each connected device, and the change typically arrives in minutes. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Your file and folder templates appear in the File Explorer right-click New menu, synced from SharePoint.
The New menu in Windows File Explorer is linked to a templates folder that syncs from SharePoint. Your own file and folder templates show up when someone right-clicks and chooses New, and the generic defaults are hidden. A folder template can add a whole set of ready-named files in one click. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Your standard reusable text and layout blocks are added to Word's Quick Parts, ready to insert in one click.
Quick Parts and Building Blocks hold the content people reuse, such as standard paragraphs and layouts. On Brand deploys yours to each person's Word, so the reusable content is the same across the team. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Office AutoCorrect and the custom dictionary carry your brand terms, product names and preferred spellings.
AutoCorrect entries go out to every device as a list file, together with custom dictionaries, so names and spellings come out right the first time. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
A desktop shortcut opens Power BI Desktop on your branded report template, which you supply or we host.
The shortcut opens Power BI Desktop on your company report template, so a new report starts on brand and does not have to be rebuilt. The template file comes from you, or we host it for you. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
A setup guide and content pack carry your brand into Canva's Brand Kit, Brand Templates and Brand Guidelines.
You get an ordered guide for setting up your Canva Brand Kit, Brand Templates, template locks and approvals, plus a paste-ready content pack with your colours, fonts, logo checklist and brand voice samples. It also fills in Canva's shareable Brand Guidelines document. You need your own Canva plan, and locks and approvals on Brand Templates need Canva Teams or Enterprise.
A portrait 9:16 PowerPoint deck in your brand, sized for TikTok, Reels and Shorts, made on request.
The deck has three layouts that you can mix: text, a large screenshot and a quote. They keep clear of the areas that each platform covers with its own captions and buttons. The deck uses the same colours, fonts and logo as your standard deck, and it is made when you ask for it.
Word's Quick Styles gallery shows only your brand's styles.
Off-brand styles come out of the gallery, so your company styles are the only ones people see and the brand is the one they reach for.
Pasting follows your brand styles, so formatting from other places does not come along.
Word's automatic bullets and numbering formats are replaced with your brand's.
PowerPoint offers only your branded enterprise themes, and the built-in themes are hidden.
OneNote starts with your brand font and basic formatting, set up to stay flexible.
Formatting that departs from your brand is flagged visually.
Excel table styles are locked to your brand's style.
Your dictionary of brand terms is uploaded to Microsoft 365 Copilot.
The dictionary is uploaded once at the tenant level, so Microsoft 365 Copilot works with your company's own terms.
People sign in to Windows with biometrics or a PIN, and the screen locks after two minutes.
Windows Hello for Business uses biometrics or a PIN of at least eight characters, and the device locks after two minutes. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Your browsers are set up with basic security settings.
The settings include SmartScreen and SSL enforcement. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Office policies harden how VBA macros, the small programs inside documents, are allowed to run.
Macros in files that come from the internet are blocked.
Your OneDrive and SharePoint sync folders are set up as Trusted Locations in Office.
Office add-ins that are not on your approved list are blocked.
Windows Update rings are set up for your devices.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Microsoft Edge opens on your homepage and startup pages and uses your brand's theme colour.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Edge shows a managed set of bookmarks and carries your Entra profile branding.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Edge's new tab page shows your branded Office 365 feed, and profile switching is set up.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Google Chrome gets policies that mirror the core settings you have in Edge.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Chrome policy templates (ADMX) are imported so that Chrome follows the same policies as Edge in full.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Your branded wallpaper and lock screen show on your devices, and people cannot change them.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Windows uses a locked theme and window accent colour from your brand palette.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
The Windows sign-in screen carries your brand.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Branded virtual backgrounds are deployed for Teams and Zoom meetings.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Every Teams meeting invite carries your logo, your legal and help links, and an AI transcript disclosure.
The footer comes from a Teams policy that applies across your whole tenant. It can carry your logo and a link to your AI use policy on every invite.
The mouse highlighter that shows on screen shares uses your brand colours.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Clipboard history and the cloud clipboard are turned on for your team.
This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Both the mouse highlighter and the spotlight use your brand colours.
Left clicks show in your primary brand colour and right clicks in your secondary colour, at an opacity that is set for you. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Custom settings for your line-of-business desktop apps, such as your code or text editors, go out to every device.
Where your team relies on industry-specific or in-house desktop software, we deploy it and push the settings it needs to each device, so the tools are set up the same for everyone. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
The Microsoft Entra ID sign-in page shows your logo and colours.
A branded sign-in page is also a security cue. When your staff expect your logo on the real page, a fake login page that is missing it is easier to spot.
OneDrive signs people in without a prompt, starts on its own and runs Known Folder Move quietly.
Known Folder Move moves a person's standard folders, such as Desktop and Documents, into OneDrive. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts.
Your Microsoft 365 app tiles and the SharePoint Brand Center are set up with your brand.
Your company's acronyms and bookmarks are uploaded to Microsoft 365 Copilot search.
People outside your company can send you files through a link and upload page that carry your branding.
File Requests give you a link that someone outside your company uses to upload files to you. The upload page shows your Entra branding. It depends on your tenant allowing Anyone links for sharing.
Your current email signature is added on the mail server as each message leaves, so nobody pastes or maintains one.
A managed tool on your mail server applies the correct company signature as each message leaves. Staff do not paste, choose or maintain a signature, and it cannot differ from one machine to another. When you change it once, it changes for everyone.
We roll your branding out to your devices in a standard rollout.
Rollout runs in stages, from a pilot group to everyone, with exclusion groups for people such as executives, marketing and IT.
The AI brand skill makes infographics in your brand when you ask for them.
The skill is a packaged file for Claude. It needs a Claude plan that supports Skills (Pro or Team), or a custom-built agent such as a Copilot agent, to install and run it.
The AI brand skill includes the Fluent icon library, coloured in your brand.
The skill is a packaged file for Claude. It needs a Claude plan that supports Skills (Pro or Team), or a custom-built agent such as a Copilot agent, to install and run it.
The AI brand skill includes a library of 24 slide layouts.
The skill is a packaged file for Claude. It needs a Claude plan that supports Skills (Pro or Team), or a custom-built agent such as a Copilot agent, to install and run it.
Nothing here yet.
No roadmap items match these filters.
Features of ProjectPoint, Governance Suite and On Brand work today. PeoplePoint and DocuPoint are coming soon. An asterisk marks what is coming soon. Each product comes in tiers, and each feature shows the tiers it is in.
Coming soon
HR in your own Microsoft 365, anchored by leave.
20 features coming soon
PeoplePoint is coming soon, and this list shows what it is planned to include.
Employees request time off and see their balance before and after. Managers approve with the balance and who else is away in one message, and an advance on leave not yet earned needs its own approval. Approved time off goes on the calendars, and annual and anniversary rollover are built in.
20 coming soon
| Feature | Time Off | Portal | Platform |
|---|---|---|---|
| Four leave types (coming soon) | Planned | Planned | Planned |
Coming soon Employees request time off as Paid, Unpaid, Sick Leave or Bereavement leave. The employee picks one of the four types on the request form. Each type has its own balance, so every kind of leave is counted separately. | |||
| Balance tracking (coming soon) | Planned | Planned | Planned |
Coming soon Each leave type shows what was allotted, what is requested and what remains. The numbers update on their own, so nobody keeps a balance spreadsheet by hand. Employees and managers work from the same figures. | |||
| Only the leave types that apply (coming soon) | Planned | Planned | Planned |
Coming soon Employees see only the leave types they have time allotted for. A type with no time allotted is hidden from that employee. Each person sees a shorter list with only the types they have time for, so there is less to sort through when they ask. | |||
| Yearly rollover for sick and bereavement leave (coming soon) | Planned | Planned | Planned |
Coming soon Sick Leave and Bereavement balances roll over once a year. | |||
| Anniversary rollover for paid leave (coming soon) | Planned | Planned | Planned |
Coming soon Paid leave for salaried employees rolls over on each work anniversary, up to a limit set for each person. Rollover happens on each person's own work anniversary, not on one shared date for the whole company. This fits salaried staff who get a fixed amount of paid leave each year. | |||
| Feature | Time Off | Portal | Platform |
|---|---|---|---|
| Request by dates, hours or days (coming soon) | Planned | Planned | Planned |
Coming soon Employees enter a start date plus an end date, a number of hours or a number of days. Employees choose whichever way is easiest for the time they need. A short absence can be booked in hours, and a longer break can be booked by dates or by a number of days, so one form covers both. | |||
| Automatic duration and balance math (coming soon) | Planned | Planned | Planned |
Coming soon Enter one value and the app works out the rest, then shows the effect on the balance. From that one entry, the app works out the length of the time off, applies the weekend and holiday rules, and shows the new balance. Employees do not count days on a calendar by hand, and the number a manager sees is already worked out. | |||
| Weekends skipped by employee type (coming soon) | Planned | Planned | Planned |
Coming soon Day counts skip weekends based on whether the employee is salaried or hourly, with a company-wide override. The app checks the employee type on each request to decide whether weekends count, so nobody has to adjust a day count by hand. A company-wide setting can override that choice when you want one rule for everyone. | |||
| Holidays left out of day counts (coming soon) | Planned | Planned | Planned |
Coming soon Day counts leave out the company and statutory holidays on your company calendar. If a company or statutory holiday falls inside the dates, that day is not counted and is not taken from the balance. People are not charged for days the company has off, and nobody has to subtract holidays by hand. | |||
| Balance before and after (coming soon) | Planned | Planned | Planned |
Coming soon Employees see their balance before and after the request while they fill it in. While the form is open, the employee sees the current balance and what it will be after the request. That lets people check the effect on their balance before they send the request, not after. | |||
| Managers request for their team (coming soon) | Planned | Planned | Planned |
Coming soon Managers can create and manage time off requests for the people who report to them. | |||
| Clean cancellation (coming soon) | Planned | Planned | Planned |
Coming soon Deleting a request restores the balance, removes the manager's calendar event and cancels the employee's invite. Cleanup runs on its own when a request is deleted, so nobody has to fix the balance or edit calendars by hand. The manager's calendar entry and the employee's invite are both cleared, so a cancelled absence does not stay behind. | |||
| Feature | Time Off | Portal | Platform |
|---|---|---|---|
| Manager approval (coming soon) | Planned | Planned | Planned |
Coming soon Each request goes to the right manager to approve or deny. The request goes to the manager or approver for that employee, so people do not have to work out who to ask. An approval is what sets off the calendar entries for the manager and the employee. | |||
| Advance approval for negative balances (coming soon) | Planned | Planned | Planned |
Coming soon If a request would take a balance below zero, the employee accepts the payback terms before the usual manager approval. This step is for businesses that let people take leave before they have earned it. The rule is built into the approval process instead of living in someone's memory. | |||
| Approval messages with the full picture (coming soon) | Planned | Planned | Planned |
Coming soon The manager's email or Teams message shows the balance after the request and who else is off at the same time. Managers decide with the facts in front of them. The message shows what the balance will be after the request and which team members are off during the same period, so there is no second app or separate calendar to open first. | |||
| Feature | Time Off | Portal | Platform |
|---|---|---|---|
| Two-sided calendar updates (coming soon) | Planned | Planned | Planned |
Coming soon When a request is approved, the manager gets a calendar event and the employee gets an invite to accept. The manager's event shows the absence without blocking the manager's own time, and there is nothing for the manager to accept. The employee gets one invite and accepts it like any other calendar invite. Both are created when the request is approved, so nobody copies dates into a calendar by hand. | |||
| See who else is away (coming soon) | Planned | Planned | Planned |
Coming soon Employees can see when teammates are away, which helps them avoid scheduling conflicts. | |||
| Company holidays in view (coming soon) | Planned | Planned | Planned |
Coming soon Employees see company holidays while they plan and submit requests. | |||
| Feature | Time Off | Portal | Platform |
|---|---|---|---|
| Company and manager settings (coming soon) | Planned | Planned | Planned |
Coming soon Admins and managers set the rules the app follows, such as the weekend override. Some settings apply to the whole company and others are set at the manager level. The weekend rule is one example of a company-wide setting. | |||
| Feature | Time Off | Portal | Platform |
|---|---|---|---|
| Time off report (coming soon) | Planned | Planned | Planned |
Coming soon A built-in report summarizes time off data for the team. | |||
Coming soon: on the roadmap, not available yet. Open one to read more. Planned tiers can change, and a blank cell means the tier is not decided yet.
No features match these filters.
A project management suite on SharePoint, starting with a site for each client.
Read more on our blog: ProjectPoint posts (opens our blog in a new tab)
9 features available now
| Feature | Registry | Portfolio | Platform |
|---|---|---|---|
| A site for each client | Included | Included | Included |
A button creates one SharePoint site for each client, ready for that client's projects. Your project manager runs it from a button on the client's record, so nobody builds a site by hand. If that client already has a site, ProjectPoint uses it and does not make a second one. The site also holds a list of that client's projects, and each new project gets its own Teams channel in the client's team. | |||
| A Teams channel for each project | Included | Included | Included |
A button adds a Teams channel for each new project in its client's team and adds the project team as members. Start it from the project's record. If the client has no site yet, ProjectPoint creates it first. The team talks in the channel, files shared there are kept in the client's site, and an email confirms when the channel is ready. | |||
| Joins your hub site | Included | Included | Included |
New client sites join your SharePoint hub, which needs only the hub owner's permissions once a SharePoint admin has registered the hub. A SharePoint admin registers your hub one time, before the first client site is made. After that, each new client site joins the hub as it is created, and the hub owner's permissions are all it takes. Your client sites then sit together under one hub. | |||
| No tenant-wide app consent | Included | Included | Included |
Provisioning runs on the site owner's own permissions, with no tenant-wide app consent and no elevated role needed to run it. ProjectPoint works through connections that belong to the site owner who installs it. It does only what that owner can already do in SharePoint, so running a provisioning needs no tenant-wide app consent and no elevated role. Your own settings still apply, such as who may create sites, and a SharePoint admin registers your hub once. | |||
| Feature | Registry | Portfolio | Platform |
|---|---|---|---|
| Central project registry | Included | Included | Included |
One list keeps every project with its client and a link to its Teams channel. Every project is one entry in a single list in your own Microsoft 365. Each entry names the client and links to the project's Teams channel. The same button that makes the channel adds the link, so nobody has to paste it in. | |||
| Feature | Registry | Portfolio | Platform |
|---|---|---|---|
| Project time entry app | Not included | Included | Included |
Team members log time against a project and a category, with save and new for quick entry. Pick the project and the category, add your time, and save. Save and new opens a blank form so you can enter several in a row, and you can reopen a saved entry to correct it. The entries stay in your own Microsoft 365. | |||
| Time entry from your browser | Not included | Included | Included |
A browser extension for Chrome and Edge logs time with start and stop timers and shows your day and week against budget. The timer sits in the browser side panel, so it is there on whatever tab you are working in, and you can type notes while the work is on screen. When several timers run at once, the time is split evenly, so your total always matches the real time that passed. Your week view marks any workday with nothing logged, and the month view says whether you are on pace. | |||
| Feature | Registry | Portfolio | Platform |
|---|---|---|---|
| Weekly summary for project managers | Not included | Included | Included |
Project managers get a weekly email that sums up the time logged on their projects. The email adds up the hours your team logged, and the numbers are in the email itself, so a project manager can read the week without opening a report. It is sent without anyone building it by hand. | |||
| Daily and weekly progress emails | Not included | Included | Included |
Daily and weekly emails show hours logged against budget, and the weekly email adds an AI-written progress summary. The daily and weekly emails show who logged what and which projects are on track against budget. The weekly email also carries a plain-English summary that AI writes from the time entries. The answer is in the email, so managers can see where each project stands without logging in and clicking through screens. | |||
No features match these filters.
Coming soon
Document tagging, assembly and deep search inside SharePoint.
14 features coming soon
DocuPoint is coming soon, and this list shows what it is planned to include.
| Feature | Tagging | Complete |
|---|---|---|
| One-click setup (coming soon) | Planned | Planned |
Coming soon Setup creates the libraries, content types and site columns for you. | ||
| Feature | Tagging | Complete |
|---|---|---|
| Metadata in the right column types (coming soon) | Planned | Planned |
Coming soon Extracted dates land in Date columns and numbers land in Number columns, not plain text. Because the values are real dates and real numbers, you can filter a library view by a date range. Columns that hold dates as plain text cannot do that. DocuPoint fills them in from the document, so nobody has to type them. | ||
| Columns that match your documents (coming soon) | Planned | Planned |
Coming soon DocuPoint creates and updates site columns and content types to match the fields it finds. When DocuPoint finds a field on a document, it adds or updates the matching site column and content type, so nobody has to build them by hand. These columns live on your own SharePoint libraries. The details stay there if you remove DocuPoint. | ||
| The right AI model for each file (coming soon) | Planned | Planned |
Coming soon DocuPoint picks among several AI Builder models by file type, rule or folder, all set from one settings list. DocuPoint can use more than one AI Builder model, so each kind of document can be read by a model chosen for it. A central settings list in SharePoint holds the choices, based on the file type, a rule or the folder. You manage them in that one place. | ||
| Automatic document type detection (coming soon) | Planned | Planned |
Coming soon An AI classifier works out what kind of document arrived, so nobody has to pick a model by hand. The classifier looks at a document's title and context to work out what type it is, then picks the model that fits that type. People do not have to tell DocuPoint what type each document is. | ||
| Review and correct extracted data (coming soon) | Planned | Planned |
Coming soon A validation app lets people check and edit the extracted values, including tables and line items. A person reviews the extracted data in the validation app and fixes anything that is wrong. This works for tables and line items as well as single values. Someone can correct one wrong line instead of rejecting the whole document. | ||
| Automatic filing (coming soon) | Planned | Planned |
Coming soon Documents move to the right folder or library by type, metadata or rule, and keep their Document ID when they move. DocuPoint files each document for you, so nobody has to sort new files by hand. It uses the document's type, its metadata or a rule to choose the folder or library. SharePoint's Document ID keeps the file traceable when it moves within the site collection. | ||
| Full text from every document (coming soon) | Planned | Planned |
Coming soon DocuPoint reads the full text of each document with OCR and stores it for search and later steps. OCR is software that reads the text on a page, including a scanned page. DocuPoint stores the full text, not only the fields it pulls out, so it can be used for search and by the steps that follow. | ||
| AI document summary (coming soon) | Planned | Planned |
Coming soon An AI-written summary of each document is saved in a SharePoint column. The summary is saved as ordinary SharePoint metadata on your own library, with no separate database. It stays with the document if you remove DocuPoint. | ||
| Feature | Tagging | Complete |
|---|---|---|
| Assemble one PDF from many files (coming soon) | Not planned | Planned |
Coming soon Assembly builds one PDF from files you choose by metadata, in one folder or across several. Assembly suits packages such as a handover dossier or a claims file. A metadata filter picks the files, and DocuPoint joins them into one PDF, so nobody has to find and merge them by hand. | ||
| Cover page from your Word template (coming soon) | Not planned | Planned |
Coming soon Each assembled PDF opens with a cover page made from an ordinary Word template you can edit, filled with details from the record. The template is an ordinary Word file stored in SharePoint. When your logo changes, someone on your team edits the Word file. Each time DocuPoint builds a package, it fills the cover with details from the record that started it. | ||
| Automatic table of contents (coming soon) | Not planned | Planned |
Coming soon Each assembled PDF gets a table of contents built from the files inside it. DocuPoint builds the table of contents each time it assembles a PDF, from the files that went into that PDF. Nobody has to write or update the list by hand. | ||
| Pages that name missing documents (coming soon) | Not planned | Planned |
Coming soon When an expected document is missing, the assembled PDF includes a placeholder page that names it. The placeholder page sits in the position where the missing document belongs, so the gap is easy to see when someone reads the PDF. | ||
| Feature | Tagging | Complete |
|---|---|---|
| Deep Search (coming soon) | Not planned | Planned |
Coming soon Search content that SharePoint search normally skips, such as tables stored inside a document's metadata. It is built for a specific need, such as finding a serial number on one invoice line item. DocuPoint filters the rows of a table stored in a document's metadata, which normal SharePoint search does not look inside. It is a targeted tool and does not replace SharePoint search. | ||
Coming soon: on the roadmap, not available yet. Open one to read more. Planned tiers can change, and a blank cell means the tier is not decided yet.
No features match these filters.
Guardrails for Power Platform makers, installed in your own tenant.
11 features available now
| Feature | Foundation | Operations | Managed |
|---|---|---|---|
| One place for environment variables | Included | Included | Included |
Admins view and edit every environment variable from one app, without opening each flow or app. An environment variable is a saved setting that apps and flows can read. The fonts and colours in the Suite's branding kit are stored this way, and this app lists them alongside all your other environment variables. Your admin can change any of them in one place. | |||
| Feature | Foundation | Operations | Managed |
|---|---|---|---|
| Branded canvas app template | Included | Included | Included |
New canvas apps start with your fonts and colours already applied to classic controls. Makers who start from the template do not have to set fonts and colours by hand, so new apps look like they belong to your company. The template reads its fonts and colours from settings stored in your own environment. Apps you built before are not changed by it, and applying your branding to them is separate work. | |||
| Your logo and loading spinner | Included | Included | Included |
The app template shows your logo and loading spinner from files on the web or in SharePoint. The spinner is the moving image people see while an app loads. Your logo and spinner files can sit on a public web page or stay private in SharePoint, and the template picks them up from there. Making a new custom spinner is separate creative work. | |||
| Rebrand template apps at once | Included | Included | Included |
Fonts and colours come from environment variables, so a rebrand takes a few clicks and no app republishing. Every font and colour in the canvas app template is read from an environment variable, which is a saved setting. To rebrand, your admin changes those settings and apps built from the template follow, so no one has to republish each app. Apps built another way are not covered, and applying your branding to them is separate work. | |||
| Model-driven app theme | Included | Included | Included |
One central theme file sets the colours of your model-driven apps. A model-driven app is a kind of Power Apps app that is built around your business data. You keep your brand colours in one theme file, and your model-driven apps take their colours from it, so a colour change is made once and not app by app. | |||
| Feature | Foundation | Operations | Managed |
|---|---|---|---|
| New app alerts | Included | Included | Included |
When someone creates a canvas or model-driven app, the maker and your helpdesk get an email. The email goes out when the app is created, so your helpdesk hears about it at the start and not only after something breaks or the maker has left. Who receives the alerts is set during setup. A maker can agree to stop getting these emails for a set number of days, and they start again by themselves. | |||
| New flow alerts | Included | Included | Included |
When someone creates a Power Automate flow, an email alert goes out. The email goes out when the flow is created, so someone in your organisation knows it exists from the start. That way a flow is not first noticed when it fails or when its maker has left. A maker can agree to stop getting these emails for a set number of days, and they start again by themselves. | |||
| Opt-out for creation alerts | Included | Included | Included |
Makers can agree to pause creation alerts for a set number of days, and the alerts turn back on by themselves. A maker fills in a consent form. After that, the Suite stops sending that maker app and flow creation alerts until the pause ends, then starts again on its own. The pause applies to that maker only, and it always ends, so the alerts cannot stay off for good. | |||
| Feature | Foundation | Operations | Managed |
|---|---|---|---|
| Error handling pattern for flows | Included | Included | Included |
A sample flow shows how to send an email and Teams alert, with a link to the failed run, when any step fails. The alert carries a link named after the flow, and the link opens the exact run that failed. Whoever gets the email or Teams message can start at the problem instead of searching for it. Because it is a sample flow, people who build flows can copy the same pattern into their own. | |||
| Suspended flows turned back on | Included | Included | Included |
A daily check turns back on flows that Power Automate switched off for the most common reasons. This keeps a flow that Power Automate switched off after a temporary failure from staying off without anyone noticing. The check runs by itself once a day. It uses a service identity, an account made for the job and limited to the actions it needs, not a personal account. | |||
| Feature | Foundation | Operations | Managed |
|---|---|---|---|
| Maker access by security group | Included | Included | Included |
Only members of a chosen security group can make apps in the default environment, and a daily check keeps it that way. By default, every licensed user can build in the default environment. Your admin picks the security group, and the Suite updates maker access whenever the group changes. A daily check covers the case where Microsoft resets the setting. | |||
No features match these filters.
Your brand, deployed inside your own Microsoft 365.
58 features available now
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Branded templates in File > New | Included | Included | Included |
Your branded Word, PowerPoint, Excel and Outlook templates appear in the File > New gallery. | |||
| Branded document themes | Included | Included | Included |
Word, PowerPoint and Excel carry a document theme that matches your brand. A theme sets the colours and fonts that a document draws on. These themes are made from your brand and added to Word, PowerPoint and Excel. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Word default template replaced | Not included | Included | Included |
A new blank Word document opens already styled in your brand. Word builds each new blank document from a default template file called Normal.dotm. On Brand replaces that file with a branded one, so a blank document already carries your brand. The deployment backs up the existing default before it replaces it. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Outlook default email template replaced | Not included | Included | Included |
New emails in Outlook start from a branded default template. The default template for new Outlook messages is a file called NormalEmail.dotm. On Brand replaces it with a branded one, and the deployment backs up the existing default first. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Excel default workbook replaced | Not included | Included | Included |
A new blank Excel workbook starts from your branded default. The default file that Excel uses for a blank workbook is called Book.xltx. On Brand replaces it with a branded one, so a new workbook starts on brand. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| PowerPoint default theme replaced | Not included | Included | Included |
A new PowerPoint deck starts from your branded default theme. The default theme is what a blank presentation opens with. On Brand replaces it with your branded theme. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| File > New shows branded templates only | Not included | Included | Included |
The File > New gallery lists only your own branded templates. | |||
| SharePoint templates library synced to devices | Not included | Included | Included |
Your templates live in one SharePoint library that syncs to each connected device, so a change usually reaches people in minutes. You update your templates in one SharePoint library. OneDrive syncs it to each connected device, and the change typically arrives in minutes. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Company templates in the right-click menu | Not included | Not included | Included |
Your file and folder templates appear in the File Explorer right-click New menu, synced from SharePoint. The New menu in Windows File Explorer is linked to a templates folder that syncs from SharePoint. Your own file and folder templates show up when someone right-clicks and chooses New, and the generic defaults are hidden. A folder template can add a whole set of ready-named files in one click. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Word Quick Parts deployed | Not included | Not included | Included |
Your standard reusable text and layout blocks are added to Word's Quick Parts, ready to insert in one click. Quick Parts and Building Blocks hold the content people reuse, such as standard paragraphs and layouts. On Brand deploys yours to each person's Word, so the reusable content is the same across the team. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| AutoCorrect custom dictionary deployed | Not included | Not included | Included |
Office AutoCorrect and the custom dictionary carry your brand terms, product names and preferred spellings. AutoCorrect entries go out to every device as a list file, together with custom dictionaries, so names and spellings come out right the first time. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Branded Power BI report template shortcut | Not included | Not included | Included |
A desktop shortcut opens Power BI Desktop on your branded report template, which you supply or we host. The shortcut opens Power BI Desktop on your company report template, so a new report starts on brand and does not have to be rebuilt. The template file comes from you, or we host it for you. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Canva Setup Kit | Not included | Included | Included |
A setup guide and content pack carry your brand into Canva's Brand Kit, Brand Templates and Brand Guidelines. You get an ordered guide for setting up your Canva Brand Kit, Brand Templates, template locks and approvals, plus a paste-ready content pack with your colours, fonts, logo checklist and brand voice samples. It also fills in Canva's shareable Brand Guidelines document. You need your own Canva plan, and locks and approvals on Brand Templates need Canva Teams or Enterprise. | |||
| Vertical short-form video deck | Not included | Included | Included |
A portrait 9:16 PowerPoint deck in your brand, sized for TikTok, Reels and Shorts, made on request. The deck has three layouts that you can mix: text, a large screenshot and a quote. They keep clear of the areas that each platform covers with its own captions and buttons. The deck uses the same colours, fonts and logo as your standard deck, and it is made when you ask for it. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Word Quick Styles locked to your brand | Not included | Included | Included |
Word's Quick Styles gallery shows only your brand's styles. Off-brand styles come out of the gallery, so your company styles are the only ones people see and the brand is the one they reach for. | |||
| Paste behaviour enforced | Not included | Included | Included |
Pasting follows your brand styles, so formatting from other places does not come along. | |||
| Auto-bullets and numbering replaced | Not included | Included | Included |
Word's automatic bullets and numbering formats are replaced with your brand's. | |||
| PowerPoint themes limited to your brand | Not included | Included | Included |
PowerPoint offers only your branded enterprise themes, and the built-in themes are hidden. | |||
| OneNote defaults | Not included | Included | Included |
OneNote starts with your brand font and basic formatting, set up to stay flexible. | |||
| Formatting inconsistencies flagged | Not included | Included | Included |
Formatting that departs from your brand is flagged visually. | |||
| Excel table style locked | Not included | Not included | Included |
Excel table styles are locked to your brand's style. | |||
| Copilot custom brand vocabulary | Not included | Not included | Included |
Your dictionary of brand terms is uploaded to Microsoft 365 Copilot. The dictionary is uploaded once at the tenant level, so Microsoft 365 Copilot works with your company's own terms. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Windows Hello for Business | Included | Included | Included |
People sign in to Windows with biometrics or a PIN, and the screen locks after two minutes. Windows Hello for Business uses biometrics or a PIN of at least eight characters, and the device locks after two minutes. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Basic browser security | Included | Included | Included |
Your browsers are set up with basic security settings. The settings include SmartScreen and SSL enforcement. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| VBA macro hardening | Not included | Included | Included |
Office policies harden how VBA macros, the small programs inside documents, are allowed to run. | |||
| Internet macro blocking | Not included | Included | Included |
Macros in files that come from the internet are blocked. | |||
| Trusted Locations for OneDrive and SharePoint | Not included | Included | Included |
Your OneDrive and SharePoint sync folders are set up as Trusted Locations in Office. | |||
| Add-in management with an allowlist | Not included | Included | Included |
Office add-ins that are not on your approved list are blocked. | |||
| Windows Update ring configuration | Not included | Included | Included |
Windows Update rings are set up for your devices. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Edge homepage and theme | Included | Included | Included |
Microsoft Edge opens on your homepage and startup pages and uses your brand's theme colour. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Edge managed bookmarks and Entra branding | Not included | Included | Included |
Edge shows a managed set of bookmarks and carries your Entra profile branding. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Edge new tab page and profile switching | Not included | Included | Included |
Edge's new tab page shows your branded Office 365 feed, and profile switching is set up. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Google Chrome basic policies | Not included | Included | Included |
Google Chrome gets policies that mirror the core settings you have in Edge. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Chrome policies matched to Edge | Not included | Not included | Included |
Chrome policy templates (ADMX) are imported so that Chrome follows the same policies as Edge in full. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Wallpaper and lock screen | Included | Included | Included |
Your branded wallpaper and lock screen show on your devices, and people cannot change them. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Windows theme and accent colours | Not included | Included | Included |
Windows uses a locked theme and window accent colour from your brand palette. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Login screen branding | Not included | Included | Included |
The Windows sign-in screen carries your brand. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Start Menu layout | Not included | Included | Included |
The Start Menu opens with a layout of pinned apps that you choose. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Teams and Zoom virtual backgrounds | Not included | Included | Included |
Branded virtual backgrounds are deployed for Teams and Zoom meetings. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Teams meeting-invite branding | Not included | Included | Included |
Every Teams meeting invite carries your logo, your legal and help links, and an AI transcript disclosure. The footer comes from a Teams policy that applies across your whole tenant. It can carry your logo and a link to your AI use policy on every invite. | |||
| On-screen brand touches | Not included | Included | Included |
The mouse highlighter that shows on screen shares uses your brand colours. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Clipboard history and paste management | Not included | Included | Included |
Clipboard history and the cloud clipboard are turned on for your team. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| On-screen brand touches, full | Not included | Not included | Included |
Both the mouse highlighter and the spotlight use your brand colours. Left clicks show in your primary brand colour and right clicks in your secondary colour, at an opacity that is set for you. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Line-of-business desktop app settings | Not included | Not included | Included |
Custom settings for your line-of-business desktop apps, such as your code or text editors, go out to every device. Where your team relies on industry-specific or in-house desktop software, we deploy it and push the settings it needs to each device, so the tools are set up the same for everyone. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Entra ID sign-in page branding | Included | Included | Included |
The Microsoft Entra ID sign-in page shows your logo and colours. A branded sign-in page is also a security cue. When your staff expect your logo on the real page, a fake login page that is missing it is easier to spot. | |||
| OneDrive silent sign-in and Known Folder Move | Included | Included | Included |
OneDrive signs people in without a prompt, starts on its own and runs Known Folder Move quietly. Known Folder Move moves a person's standard folders, such as Desktop and Documents, into OneDrive. This needs Microsoft Intune already set up in your tenant. If you are not there yet, we scope a short remediation phase before branding starts. | |||
| App tiles and SharePoint Brand Center | Not included | Included | Included |
Your Microsoft 365 app tiles and the SharePoint Brand Center are set up with your brand. | |||
| Copilot search acronyms and bookmarks | Not included | Included | Included |
Your company's acronyms and bookmarks are uploaded to Microsoft 365 Copilot search. | |||
| Branded File Requests | Not included | Included | Included |
People outside your company can send you files through a link and upload page that carry your branding. File Requests give you a link that someone outside your company uses to upload files to you. The upload page shows your Entra branding. It depends on your tenant allowing Anyone links for sharing. | |||
| SharePoint content types | Not included | Not included | Included |
The New menu in your SharePoint document libraries offers your branded templates. The content types are created once for your whole tenant, so each document library offers the same branded templates in its New menu. | |||
| Server-side email signatures | Not included | Not included | Included |
Your current email signature is added on the mail server as each message leaves, so nobody pastes or maintains one. A managed tool on your mail server applies the correct company signature as each message leaves. Staff do not paste, choose or maintain a signature, and it cannot differ from one machine to another. When you change it once, it changes for everyone. | |||
| SharePoint custom navigation and footer | Not included | Not included | Included |
Your SharePoint sites get a custom navigation extension and a footer bar. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Standard rollout | Included | Included | Included |
We roll your branding out to your devices in a standard rollout. | |||
| Pilot, broad rollout and exclusion groups | Not included | Not included | Included |
Rollout runs in stages, from a pilot group to everyone, with exclusion groups for people such as executives, marketing and IT. | |||
| Feature | Ready | Pro | 365 |
|---|---|---|---|
| Branded infographic generator | Not included | Included | Included |
The AI brand skill makes infographics in your brand when you ask for them. The skill is a packaged file for Claude. It needs a Claude plan that supports Skills (Pro or Team), or a custom-built agent such as a Copilot agent, to install and run it. | |||
| Icon system | Not included | Not included | Included |
The AI brand skill includes the Fluent icon library, coloured in your brand. The skill is a packaged file for Claude. It needs a Claude plan that supports Skills (Pro or Team), or a custom-built agent such as a Copilot agent, to install and run it. | |||
| Slide-pattern library | Not included | Not included | Included |
The AI brand skill includes a library of 24 slide layouts. The skill is a packaged file for Claude. It needs a Claude plan that supports Skills (Pro or Team), or a custom-built agent such as a Copilot agent, to install and run it. | |||
No features match these filters.