EP365 Private secure AI a private AI assistant inside your Microsoft 365

No. The assistant calls an AI model hosted in your own Azure subscription in an EU region. Microsoft contractually guarantees that your content is not used to train models and does not leave your company. We only have access to a service account for deployment and support — you can revoke it at any time.

Yes, if you want it to. You turn on answers from documents with a toggle right next to the query field: before answering, the assistant searches your SharePoint, replies with links to the sources and shows which documents it drew on — click to open a preview straight in the application. The scope (the whole company, a specific site, selected libraries) is set by the administrator, and you can narrow it further in your question. No copy of the data is created in the process. Alongside this, attachments work too — you attach a specific file to a given conversation.

No. It searches under the specific user's identity and trims results by permissions. The application has no account with broader access to content — so two colleagues can get different answers to the same question depending on what each of them is allowed to see. For oversight you can additionally enable a record: who searched for what and which sources the assistant used.

Conversations stay with you in Microsoft 365 and everyone sees only their own — someone else's conversation cannot be opened by any route. For oversight you can optionally enable administrator supervision (read-only, off by default); the user always sees a clear indicator of whether their conversations are private or visible to an administrator. Sign-in runs through the company Microsoft account, with no extra password. Attachment content is never stored — only the file name.

PDF, Word (DOCX), Excel (XLSX), PowerPoint (PPTX), TXT, MD, CSV — we read text from these. Images in JPG, PNG and WEBP. The maximum attachment size is 10 MB by default (adjustable).

Copilot is excellent inside a specific application (Word, Outlook, PowerPoint) and is paid for per user — regardless of how much each of them actually uses it. Our assistant covers the whole organisation and you pay only for actual usage (the number of AI actions per month): chat on the company page and in the floating widget, answers from documents with links to the source, shared prompts, per-person daily limits and a cost overview for administrators. We often deploy both — side by side, not instead of one another.

Yes. Beyond answering from documents, it also works with your own mailbox and calendar — under your sign-in and only with your data. It prepares a morning brief (meetings, mail awaiting a reply, tasks), drafts a reply to an email, triages your mail or turns a meeting into minutes. But it never sends or deletes anything: replies and emails are saved as Outlook drafts, tasks go into Microsoft To Do in one click, and the final step is always yours. An administrator enables the whole area (a one-time approval of Microsoft permissions) and can switch it off at any time.

Yes. From a conversation or from company knowledge it writes a document — a summary, a piece on a topic with source links, a comparison of versions, or the content of a new web page. Download the result as Word, Markdown or HTML, save it to a chosen SharePoint library, or turn it straight into a SharePoint page. It prepares social media posts the same way (LinkedIn, for example) and saves them to a library as .md — so it then knows them and you can ask “what did we post about…” or have it follow up on an earlier post. Everything is created under your sign-in and only over your data; the final step (publishing, sending) stays with you.

Every user has a daily query limit (50 by default, adjustable). In the application the administrator has an overview with monthly spend, consumption, a daily chart and the top 10 most active people. Re-running an answer doesn't count against the daily limit.

Take a company of 60 people. The start is measurement only: people make 380 AI actions in the first month without the company paying anything. Then paying starts: 380 actions place the company in the up-to-800 band at CZK 3,900 a month — we always invoice in advance, so you know the amount at the start of the month. Usage grows gradually (640, then 900 actions), but the rolling average of recent months stays under 800, so the company keeps paying CZK 3,900. Only when the average exceeds 800 (in the example in month 5, after a 1,250-action month) does the company move to the up-to-1,500 band at CZK 6,900 from the following month — you always know about a band change in advance, and it works downwards too when usage drops. For comparison: Microsoft 365 Copilot would cost the same company ~CZK 39,000 a month (CZK 650 × 60 people) regardless of usage. You'll find a visual version of this story and a calculator right in the Pricing section.

Getting the chat technically up and running is a matter of a few hours. A full company rollout (installation, configuration, training) takes 5–10 working days from the kick-off call, Starter (one site / one department) 3–5 days. Larger rollouts we handle individually, according to scope and regulatory requirements.

Yes — across three levels. Personal templates are seen only by their owner. Team templates (created by the site administrator) are seen by everyone in the team. Company templates are managed centrally by the administrator and seen by the whole organisation. Every template has an icon, a colour, a name and the prompt text.

Microsoft 365 with SharePoint Online — what most companies already pay for — and your own Azure subscription where the AI model will run. Nothing is installed on computers or phones; people sign in with their company account. We'll help you with everything else during deployment.

None — and the licence follows actual usage, so you only pay for what the assistant really does. Just budget for running the AI model — that comes straight from your Azure subscription (typically ~CZK 0.10–0.40 per action) and you see the daily trend in the overview. Measurement comes first at the start, so you know your real volume before you pay anything.

You upload the package to your App Catalog just once. New versions are then activated by your admin right inside the app — in Settings, on the Version management card — including rolling back to an earlier version. No repeated package deployments: we ship improvements continuously and you choose when to switch.