Copilot and Cowork: what is changing for Swiss SMEs

A new name, a new interface and several new capabilities: following Microsoft's announcements can leave a business wondering whether it needs an entirely different AI solution again. For Swiss SMEs, the more useful questions are straightforward. Which work can you delegate today, which functionality is still experimental, and who is accountable for the result?

This article reviews the position on 30 September 2026. It separates official product information from our recommendations. The focus is the changes to Copilot and Cowork, rather than another general business case for a Copilot pilot. Your IT owner should verify availability in your own tenant.

Our assessment is that the significant shift is from an individual answer to a traceable work assignment. This makes the quality of the brief more important. An organisation with unclear processes does not gain clear accountability merely by adopting a new interface. That is where smaller businesses should begin.

Microsoft 365 Copilot Cowork is Microsoft's offering for delegated, multi-step work. It is a different product from Anthropic's Claude Cowork. Microsoft announced worldwide general availability for Microsoft 365 Copilot customers on 16 June 2026. The general availability announcement also describes additional consumption billing.

For purchasing decisions, record the product, user licence, enabled capability, model and billing arrangement separately. A visible Copilot button does not establish which capabilities your business has purchased or approved. Nor does using the same underlying model mean that two products have the same access to business data.

Use the full product name in internal guidance. “Do this with Cowork” is an ambiguous instruction when employees know different services. Include the intended company sign-in and approved information sources. That small clarification can prevent misunderstandings before anyone changes a technical setting.

The 25 September announcement positions Home as a shared starting point for Chat, Cowork and Office editing. Code is intended for building small applications. Autopilot, formerly Scout, is a persistent personal agent.

Base operational commitments on capabilities you have actually verified. A roadmap indicates direction; it is not a delivery commitment for your own business.

The Cowork release notes list September support for editing existing Office files in OneDrive and SharePoint while retaining version history, additional model options and an App skill in Frontier. Local Edge browser use is listed as generally available since August. Event-driven tasks are also documented.

Our practical recommendation is to investigate work on existing documents first. Maintaining one authoritative document may be more useful than producing a new file every time. Specify the authoritative file, the sections that may change and the person who will approve the revision.

A weekly project update is one possible example. The assignment uses an agreed template and approved sources. New information is dated, and uncertainty is recorded as an open issue. Before distribution, the project lead checks the content and recipients. This is a suggested scenario, not a claimed customer result.

The same principle applies to small applications. A working prototype is a useful starting point for discussion. Operational use additionally needs an accountable owner, a clear description and a way to report problems. Otherwise, an unmanaged collection of AI-built applications simply joins the existing spreadsheet estate.

Microsoft documents Cowork access through applicable spending policies. Under Copilot → Cost Management → Configuration, check which policies include which people and select Cowork. A small credit limit does not deny access. Limit enforcement is also asynchronous.

The billing documentation covers group policies, alerts and payment arrangements. Pay particular attention to “Auto-apply new services”: future supported services can thereby be added to an existing policy automatically.

We recommend a short written approval record for each new use: intended user group, confirmed licence requirements, billing relationship, budget owner and review date. Ask your provider to confirm the components covered by your contract. General availability does not imply free use or universal entitlement under every existing licence.

Do not copy a US price into a Swiss budget without checking it. Contract currency, tax, purchasing route and consumption must match your own invoice. A small business does not need a large financial management initiative to start. An identified owner and regular review of actual expenditure provide a practical first step.

Microsoft's minimum requirements include an assigned Copilot licence with an eligible prerequisite licence, suitable identities and supported platforms. Mailbox grounding requires the primary mailbox to reside in Exchange Online. The licensing overview also distinguishes included web-based Copilot Chat from work-based chat requiring a Copilot licence.

Microsoft describes the Frontier programme as an opt-in preview route requiring a Copilot licence. This does not promise immediate access to every announced feature for every participant. Current access and billing settings also determine the actual Cowork enablement.

Our recommendation is to have IT perform the check using an intended participant's account. An administrator may see different capabilities from the eventual user group. Document both an allowed access case and a person who is intentionally excluded. Check effective controls, rather than relying on the name of a group.

The quality of the starting documents is equally important. Choose a small, maintained information set for the first assignment. Obsolete drafts and authoritative documents should be distinguishable. If a human cannot determine which version is valid, resolve that question before introducing an automated assignment.

Finally, decide where results belong. A draft in a personal location is different from a shared working document. Specify when the result changes status and who is responsible. This makes the handover from AI assistance into the normal business process explicit.

Microsoft's model overview distinguishes models and providers. Auto selects from permitted options; higher reasoning effort can take longer and consume more credits. Review the linked processing information for the particular model you intend to use.

For Swiss SMEs, we recommend a simple information rule: which data may be processed in which approved service? Explain the answer through examples. Public product information, internal project documents and particularly sensitive contract details should not receive identical treatment without review.

Do not interpret an enterprise interface as a promise that all processing occurs exclusively in Switzerland. Have your required conditions confirmed against the actual configuration and contractual documentation. This article makes no blanket claim of Swiss data residency across all models and capabilities.

If help pages conflict or interfaces differ, a documented clarification is more useful than an improvised workaround. Record the product, capability, date and affected user group. This makes the answer reviewable when a subsequent rollout changes a setting.

The examples below are ZUMENTIQ's own suggestions. Each deliberately starts with a limited assignment and an outcome someone can inspect. A broad instruction such as “organise our sales operation” leaves too many decisions unresolved.

Before the first attempt, state what is explicitly outside the assignment. For a project report, this might include budget approvals, delivery date changes and external distribution. Put those boundaries into the brief and ensure they are consistent with the controls actually available.

A useful brief specifies the result, sources, scope and approval: “Create an internal decision draft from these three approved documents. Separate supported facts from assumptions. List conflicting information. Do not send anything.” This makes quality easier to assess than judging the fluency of a polished answer.

Microsoft describes user permissions, approvals and logging for automated Cowork tasks in its administration documentation. The user guide explains reviewing and approving actions. Granting a permission does not transfer business accountability.

Specify what should happen when information is missing, recipients are uncertain or numbers conflict. For an internal report, saving a draft and notifying the owner may be a useful fallback. External distribution needs particularly clear authorisation. The next step should remain traceable in either case.

Deliberately test a failure scenario. In a suitable test environment, remove access to a required source or supply a document containing clearly contradictory information. What matters is whether the assignment exposes the gap. An invented value is worse than a properly reported failure.

Appoint a deputy and define how to stop the task. A recurring assignment must not become organisationally ownerless when the responsible person goes on holiday. Good automation includes knowing when it should be paused.

Start with a short inventory. Which Copilot capabilities are actually visible in the company account? Which are approved? Which billing arrangement applies? Date the answers. Then let the business department and IT select exactly one assignment from the table, or a similarly bounded process.

Reserve time during the first week for configuration, execution and review. Set an owner for the decision to continue, not just a launch date. Collect open issues in a shared location so they do not disappear into individual conversations.

After the first few runs, decide whether to refine the brief, change access, postpone the capability or expand its use in a controlled way. Waiting for more stable availability is entirely reasonable if a preview does not meet your requirements. An announcement creates no obligation to adopt.

Discuss the change with employees too. Explain which work may be delegated and where human approval remains necessary. Show a successful result and a deliberately stopped case. Both contribute to a realistic understanding of the technology.

Our conclusion: Copilot and Cowork provide more opportunities to support work across several steps. Value emerges when a clear assignment meets appropriate access, understandable expenditure and a reachable accountable owner. Start with those four elements rather than reacting to every product name with a new purchase.