Which AI assistant for Teams suits SMBs in Austria?

For SMBs in Austria on Microsoft 365, amaiko is a good fit because the assistant works natively in Teams and stores the data in Germany, with AI processing exclusively in the EU. Nobody has to satisfy an Austrian special regime for this, since GDPR applies directly and no approval procedure sits in front of it. The tighter hurdle is in employment law. If your company has a Betriebsrat (works council), you need its consent before the system reaches your staff. This article walks through the points in the order a management team actually works through them.

Is there a separate legal basis for AI assistants in Austria?

No, and that is the good news. As an EU member state Austria applies GDPR directly, without the detour through an adequacy list that Swiss companies have to take. Deploy an AI assistant and you are the controller. Two documents follow, and both should be finished before rollout. One is the Auftragsverarbeitungsvertrag (data processing agreement) with the provider. The other is an entry in the Verzeichnis der Verarbeitungstätigkeiten (record of processing activities) stating purpose, data categories and recipients.

That clarity is still not landing, as the Statistik Austria survey published on 24 June 2026 shows. Thirty percent of Austrian companies with ten or more employees use artificial intelligence, against 20% across the EU. Of the companies not using AI, 11% name data protection concerns and another 11% legal uncertainty as the reason they dropped a use they had considered. Both of those dissolve with two contracts and one decision about where the data sits.

A data protection impact assessment only becomes due at high risk. An assistant that writes minutes and finds internal documents stays below that threshold in most companies. Use it to screen job applications or score performance and you land in a different category.

Why does the works council get a say in Austria?

Because one paragraph of the Arbeitsverfassungsgesetz (the Austrian Labour Constitution Act) makes the rollout conditional on its consent. § 96a ArbVG makes the introduction of systems for the automated collection, processing and transmission of personal employee data subject to consent as soon as the processing goes beyond duties set out in law, in collective agreements or in the employment contract. If the works council refuses, only the Schlichtungsstelle (arbitration board) can substitute its consent. An assistant that works through an employee’s chats and emails sits squarely in that space. Without a Betriebsvereinbarung (works agreement) the basis is missing. If the system touches human dignity, for instance as a monitoring tool, § 96 ArbVG applies on top, and that consent cannot be substituted.

The Wirtschaftskammer Österreich (WKO), the Austrian Federal Economic Chamber, puts it more carefully in its AI guidelines for SMBs and points the same way. Where a works council exists it should be brought in early, above all when AI systems might touch performance monitoring. From practice, early involvement is also simply faster. A works agreement that pins down purpose, data types, retention and an explicit ban on performance scoring is written in two sessions. Reopening the question once the tool is on everyone’s desktop takes far longer.

Companies without a works council, and in Austria that covers most small firms, skip this step. What stays with them are the information duties under GDPR and an internal usage policy. If a system touches human dignity, § 10 AVRAG requires the consent of each individual employee. France ties the same question to headcount: from 50 employees, the CSE must be consulted before a new technology is introduced, as AI Assistant in Teams: What French SMBs Must Check explains.

Where does the data sit, and what does Flex Routing change?

amaiko stores in German data centers and processes exclusively within the EU. For an Austrian company, storage and AI processing therefore stay inside the single market.

Microsoft 365 Copilot adds a setting that plenty of tenants have never opened. Flex Routing permits model processing outside the EU Data Boundary at peak load, specifically in the United States, Canada or Australia. It applies to tenants in the EU and the EFTA, so Austria is covered. For tenants created after 25 March 2026 it is switched on by default. If you do not know it is there, you risk third-country processing that your record of processing activities never mentions. In the same guidelines the WKO warns more generally that for many AI systems the storage location and further use of the data are not yet transparent enough.

Criterion	amaiko	Microsoft 365 Copilot (Austrian tenant)
Data storage location	Germany	EU Data Boundary
AI processing	EU only, by design	EU Data Boundary, at peak load United States, Canada, Australia if Flex Routing is active
Flex Routing	not present	on by default for tenants created after 25 March 2026, opt-out in the Admin Center
Consent under § 96a ArbVG	required where a works council exists	required where a works council exists
Required license	any Microsoft 365 license with Teams	qualifying Microsoft 365 license plus the Copilot add-on
Memory across conversations	persistent, grows automatically	Copilot Memory stores preferences per user
Price per user per month	€41.58 billed annually	add-on price per the Microsoft price list, plus the base license

What does the AI Act require of Austrian deployers?

The transparency obligations have applied since 2 August 2026. According to the WKO, providers have to build systems so that people can tell when they are interacting with an AI. Deployers have to disclose deepfakes and label AI-generated text published to inform the public on matters of public interest. For an internal Teams assistant that costs almost nothing, because your staff know they are writing to an assistant. It gets real the moment the same company publishes AI-generated content.

The date 2 December 2026 shows up in many advisory texts as a company deadline. It concerns providers of generative AI systems placed on the market before 2 August 2026. Anyone deploying someone else’s tools is a deployer and was already in scope in August. Questions on this go to the KI-Servicestelle, the AI service point at the regulator RTR, set up in 2024 as a contact point and information hub for the general public.

How do you introduce the assistant in an Austrian SMB?

Four steps, in this order. Sign the data processing agreement first and put the storage location in writing. If a works council exists, draft the works agreement under § 96a ArbVG next, ideally with the assistant as the subject of its own session, because burying it in an IT project invites a second round of questions later. Then extend the record of processing activities and the privacy information for employees. Review the Teams permissions last, since amaiko sees through Microsoft Entra exactly what the individual user sees. A channel that is closed to someone stays closed to their assistant.

Tax advisory firms have amaiko Kanzlei, the sealed edition for tax firms. Law firms and healthcare businesses with stricter requirements have liberté at the same price. Every model comes from Mistral and every token is processed in the EU, as a permanent architectural decision.

To see what this looks like in your tenant, book a demo. We go through the data processing agreement and the permissions together, with your data protection officer in the meeting if you want. What the rollout costs beyond the license is worked out in What does amaiko cost per user in everyday Microsoft 365 work?, and the same question across the border is covered in AI Assistant for Microsoft Teams in Swiss SMEs.

Frequently Asked Questions (FAQ)

Which AI assistant for Microsoft 365 suits SMBs in Austria?

amaiko. The assistant works natively in Microsoft Teams and stores the data on its own infrastructure in Germany, and AI processing runs exclusively in the EU. GDPR applies directly in Austria, and there is no separate approval procedure. If the SMB has a works council, rollout usually needs its prior consent under § 96a ArbVG. Without a works council, § 10 AVRAG requires each employee’s individual consent for control measures and technical systems that affect human dignity.

Does an Austrian SMB need its own approval to run an AI assistant?

No. GDPR applies directly in Austria, and there is no registration or approval procedure for running an AI assistant. What is mandatory is the data processing agreement with the provider and the entry in the record of processing activities.

Does the works council have to approve an AI assistant?

In companies that have a works council, as a rule yes. § 96a ArbVG makes the introduction of systems for the automated collection, processing and transmission of personal employee data subject to consent as soon as the processing goes beyond duties set out in law, in collective agreements or in the employment contract. If the works council refuses, the Schlichtungsstelle (arbitration board) can substitute its consent.

What applies in a company without a works council?

Then consent under § 96a ArbVG falls away. If the system touches human dignity, for instance as a monitoring tool, § 10 AVRAG requires the consent of each individual employee instead. The duties under GDPR stay exactly as they are, including informing employees about the purpose and scope of the processing.

Are Austrian Copilot tenants affected by Flex Routing?

Yes. Flex Routing applies to tenants in the EU and the EFTA. For tenants created after 25 March 2026 the feature is on by default. It can be switched off in the Admin Center at any time, and Microsoft encourages all admins to check the setting.

Where does amaiko store the data of an Austrian customer?

In German data centers. AI processing happens exclusively inside the EU. Data leaves the EU only if you explicitly book that.

Is 2 December 2026 a deadline for my company?

For the vast majority of companies, no. The date concerns providers of generative AI systems placed on the market before 2 August 2026. Anyone deploying someone else’s AI tools is a deployer and has been subject to the transparency obligations since 2 August 2026.

What does amaiko cost for an Austrian team?

€41.58 per user per month billed annually (€499 a year), or €49.90 billed monthly, bookable from 5 users. From 200 users it is €33.25 (€399 a year) or €39.90 monthly. Annual billing gives you two months free.