IT support inside Microsoft Teams

Asked in the Teams chat. Solved right there.

For IT leads in mid-sized companies with more on their plate than hands. Someone describes a problem. Romy reads that one device in Intune and Entra ID, shows as a card what the fix would do, and runs it only once a person confirms. Then Romy checks that it worked.

Live today: reading, proposals, restarts after confirmation, Windows repairs once switched on. The Teams chat carries customer data only once the European data boundary is proven for it.

Microsoft TeamsMicrosoft IntuneMicrosoft Entra IDMicrosoft 365
§ 01The problem

The service desk spends its day on tier-1 work that needs no judgement.

A slow laptop, a frozen Teams client, a stale browser cache, a restart that never happened. Each request is small. Each still costs a full context switch.

Repetitive tickets

Small fix, full handling.

Find the device in Intune, check compliance and last check-in, trigger the remote action, wait, call back, close the ticket. The fix takes seconds; handling takes the rest.

Bundled permissions

Restart only comes with wipe.

Intune grants restart, wipe, retire and passcode reset through one permission. Handing remote actions to first line or a bot hands over all four. So most teams don’t delegate.

Chatbots stop at the answer

A knowledge article is no fix.

The person gets steps to follow, the problem stays, and the ticket comes back.

§ 02How Romy works

One workflow, as employees see it.

Scroll the steps: the chat builds up and the card is replaced in place. In the Teams chat, Romy answers only agreed pilot users today, until the data boundary is proven for Teams.

1 · Report

The person describes the problem.

In their own words, in their personal chat. Romy knows who is asking from the Microsoft sign-in, not from the text.

2 · Read

Romy reads that one device.

Only what belongs to this question, from Intune. The source is cited under the message.

3 · Propose

One card, every consequence spelled out.

How it runs, what happens, whether it can be undone, which path, how Romy checks. Plus an alternative.

4 · Confirm and run

The person confirms. Romy runs it.

Valid for 15 minutes, redeemable once, only for the device on the card. The restart goes through the Romy app on the device, otherwise through Intune.

5 · Check

Romy checks and reports the result.

For a restart, Romy reads the device’s boot time. The result replaces the card.

In Teams, Romy’s cards are in German today; this is an English rendering of the same card. Device and values are an example.

Romy proposes. A person decides. Only then does a fixed, tested workflow run.

§ 03Try it

Describe a problem. Romy shows you the way.

Romy finds the way through its knowledge graph: from topic to symptom, from symptom to the fix that runs on your device. The same routing as in the chat does the work here, without a model. Every case is reachable without typing, through the topics.

Your device
Examples
Limits
Topic

Tap a topic, then a symptom.

Symptom

Describe a problem above, pick an example or tap a topic.

Fix

Describe a problem above, pick an example or tap a topic.

Answer

Describe a problem above, pick an example or tap a topic.

What the code guarantees

Locks sit between the stages. They live in the code, and each one has a test that runs on every change. Tap a lock.

  1. Sign-in
  2. Topic → Symptom
  3. Symptom → Fix
  4. Fix → Card
  5. Card → Run
  6. Afterwards

Your sentence goes to getromy.com, through Romy's routing and back. It is not stored and no model reads it. The routing is a checked copy from the product and answers every test sentence on every device the same way.

Romy's fixed chat sentences, step questions and buttons are German in the product today, so they appear here in German, exactly as in the chat, marked DE. Topics, symptoms and examples come in English from Romy's language data, and a symptom the data has only in German carries the same DE mark.

See all use cases

§ 04Your flow

What happens to your information, step by step.

From the question to the evidence. Romy never acts without a person having confirmed.

Example: “My laptop is sluggish”

A person confirms

Nothing that changes a device runs without a confirmation. It applies only to the device on the card and expires after 15 minutes.

What this means for you

Without a confirmation, nothing happens.

§ 05What runs today

Every workflow has a mode, and the mode is honest.

Five rungs, from runs to never. Anything that changes a device always needs a confirmation.

Runs

You confirm the card and it runs.

  • Restart
  • Check device health, updates, drivers, management and network
  • Teams, Edge and Chrome cache on Windows, opt-in per company

Preview mode

Every step visible, with a badge. Nothing runs.

  • Repairs on the Mac
  • Outlook check

Answer only

Romy reads and explains, without a card.

  • Licence inventory, sign-in methods, compliance, fleet questions

Off

Built, not switched on for customers.

  • Repairs on Linux, so far only tested in the lab
  • Repairs through Intune

Never

Not selectable on any path.

  • Wipe, retire, passcode reset, user deletion

Repairs are off for every company until its admin switches them on, and can be switched off again at any time.

§ 06Setup

Three Microsoft dialogs. Rolled out with Intune.

Each stage is its own enterprise app in Entra ID, with consent for the whole organisation. The Romy app ships as a Win32 app through your Intune assignment.

1 · Read

Romy Diagnostics

Read permissions for devices, accounts, groups, Conditional Access policies, licences and usage. This app cannot change anything.

2 · Act

Romy Engage

Optional. Restart after confirmation. The Intune permission also covers wipe, retire and passcode reset; Romy cannot reach these actions on any path.

3 · Teams

Romy in Teams

Romy goes into your organisation’s Teams catalog. The Teams app itself holds no Graph permission. The chat carries customer data only once the data boundary is proven for Teams.

The full setup with every permission →

§ 07Control and audit

Every step leaves a record. Facts and timing, never content.

Request, card, confirmation and run are logged, without message text, device names or user names.

Allowed
Romy can reach only what it is explicitly allowed to. Everything else is blocked.
Never
Wipe, retire, passcode reset and user deletion are blocked on every path.
Confirmation
15 minutes, once, one device. Without it Romy changes nothing.
Repairs
Off until the admin switches them on; revocable at any time.
Operation
Azure Germany West Central (Frankfurt). No copy of your directory.
Revocation
Each app can be removed in Entra ID on its own.
§ 08Where Romy fits

Inside the Microsoft stack you already run.

No new portal for employees, no agent project for IT. Romy uses Teams, Entra ID and Intune as they are.

Installable

Microsoft Teams

Personal app with cards for proposal, progress and result. The chat carries customer data only once the European data boundary is proven for the Teams channel.

Live

Microsoft Entra ID

Three enterprise apps with admin consent. In Entra ID itself, Romy only reads.

Live

Microsoft Intune

Devices, apps and policies read. Restart through Romy Engage. The Romy app as a required Win32 app.

Live

Romy portal

For admins: setup status, devices and findings, licence inventory, the repair switch.

Live

AI clients

Romy over MCP, with a key per organisation. →

Planned

Microsoft Store

The Romy app and Teams app in Microsoft’s stores. Today the Romy app ships as a Win32 package through Intune.

Planned

Joiners and leavers

Romy assembles the package for people joining and leaving, and a person confirms.

§ 09Why Romy

Requests get finished where they are raised.

Built in Munich for Microsoft 365 companies in Europe.

Wedge

Start at the request.

The most frequent, no-judgement requests arrive by chat anyway. Romy closes them where they are raised.

Edge

Tested workflows instead of free-form commands.

Romy runs only workflows we wrote and tested ourselves. The model does not invent commands.

Trust

Delegation without the bundle.

Restarts and cache repairs can be handed to employees themselves, without giving anyone wipe or retire.

Provenance

Built to be checked.

Source code, tests and a bill of materials per build live in our GitHub Enterprise in the EU.

§ 10Questions

What you are probably thinking.

The objections from every first conversation, answered honestly.

Are we letting an AI loose in our directory?

No. Romy can reach only actions that are explicitly allowed. Wipe, retire, passcode reset and user deletion are out of reach on every path. Anything that changes a device also needs a person to confirm. The model proposes; only a fixed workflow runs.

What happens if Romy gets it wrong?

Nothing, as long as nobody confirms. A confirmation is valid for 15 minutes and can be redeemed exactly once. Expired or used confirmations lead to no action.

How much work is the setup?

Three Microsoft dialogs, each a consent for the organisation that an administrator grants in minutes and can withdraw at any time. Reading and the Intune restart need no software on the devices. You roll out the Romy app for Windows repairs through Intune. On request, sales walks you through the three steps. You click in your own Microsoft 365, and we explain each step.

Where does our data live?

Romy runs in Azure Germany West Central in Frankfurt. Romy keeps no copy of your data: fetch, prepare, return. Only the log of what was queried and what was run is kept. The Teams chat carries customer data only once the European data boundary is proven for the Teams channel.

Does this replace our service provider or our people?

No. Romy takes over the repetition. Decisions, architecture and everything that needs judgement stay with your team.

What can’t Romy do yet?

Today the device restart can run and, once an admin switches them on, a few Windows repairs. Everything else is reading, analysing and proposing. Mac repairs are in preview mode; on Linux they have only been tested in the lab.

Start read-only in your own tenant.

Grant Diagnostics first. Nothing can change until you grant Engage and someone confirms a card.