Using Microsoft Forms as a real Mac app: open it without hunting for the tab

The pattern that sends people searching for a Microsoft Forms desktop app is always the same. A form goes out on Tuesday, responses trickle in for a week, and every check means finding the right tab, or going back through a portal, or signing in again with the account that is not the default one. On Windows there is at least a Store listing to click. On a Mac there is nothing to install.

Microsoft is direct about why, and the answer shapes everything that follows.

What Microsoft publishes for a Mac

The Microsoft 365 page for Mac names the applications that exist as downloads: Word, Excel, PowerPoint, Outlook, OneNote, and OneDrive. Forms is not on that list, and there is no separate installer, disk image, or Mac App Store listing for it.

The support centre answers the desktop question in its own article, and the framing is a feature rather than an apology.

Yes. This means a broad audience can use your survey or quiz without having to download a separate app. Source: support.microsoft.com

That is the whole design. A form has to open for a respondent who has no licence, no installation, and possibly no Microsoft account at all, so the product lives on the web on every platform. Microsoft's own description of Forms says the same thing from the other side: surveys, quizzes, and polls that others answer using almost any web browser or mobile device, with results visible in real time and exportable to Excel.

The consequence for an author on a Mac is narrow. The authoring surface is a website too, and the only question left is what kind of window that website gets.

The address, and why it moved

Microsoft's sign-in instructions for Forms point at forms.office.com, and that address currently lands on forms.cloud.microsoft, part of the domain Microsoft moved its web applications to. Both work, and the redirect happens before the page renders.

This matters for one reason. Any window built around Forms has to be allowed to follow a redirect to a different domain, and often two, because the sign-in step itself runs on a Microsoft identity domain before returning. A wrapper locked to a single hostname stalls at the first hop and looks broken. Every route described below handles this correctly, but it is the first thing to check if a window opens to an error rather than a form list.

The sign-in accounts are worth reading carefully as well, because they explain a common source of confusion. Microsoft's documentation says to sign in with Microsoft 365 school credentials, Microsoft 365 work credentials, or a Microsoft account such as Hotmail, Live, or Outlook.com. Availability is described as general for Office 365 Education customers, Microsoft 365 Apps for business customers, and users with a Microsoft account. Three different identity types reach three different sets of forms, and a browser signed in to one will happily show an empty list for the other.

Two accounts means two icons

This is where a Dock icon stops being cosmetic for most people.

A teacher with a school tenant and a personal account, or a consultant who authors forms inside a client tenant while keeping company forms in another, is running two identities against the same website. In a single browser profile that means signing out and in, or living with an account picker that guesses wrong, several times a week.

Apple's documentation describes the property that solves it. A Safari web app functions independently of Safari and shares no browsing history, cookies, website data, or settings with it. Two web apps therefore hold two sessions that never see each other. One icon named for the school, one named for the company, each opening straight to the form list that belongs to it.

The same separation is available in Chrome, with a caveat: the installed app belongs to the Chrome profile it was created in, so a second identity needs a second Chrome profile before it can have a second icon. That works, and it is more machinery to maintain than most people want for a survey tool.

Naming and icons are editable after the fact in both routes, which is worth knowing because the default name will be the page title for every one of them.

Notifications arrive by email, not as a badge

Anyone hoping that an icon in the Dock will light up when a response lands should read this part before building anything.

Forms delivers author notifications through email. The response settings include an option to get an email notification of each response, and a second option for smart notifications that track response status. Microsoft describes those smart notifications as email delivered, covering engagement monitoring, reminders when enough responses have arrived to look at insights, and follow up suggestions. The reminder timing is documented: when an invited person has not submitted, the form owner receives a response status email after about 16 hours, with a button to send a reminder. The automated mail arrives from a no-reply address at forms.mail.microsoft by default, which is useful to know when building an inbox rule for it.

None of that is a push notification to macOS. A Dock badge on a web app appears only when the site asks for notification permission and sends notifications, and Apple's documentation notes that the permission must be answered inside the web app itself. Forms is not built to alert an author that way.

So the honest benefit of a Forms icon is not alerting. It is that checking results becomes a keystroke instead of a search, and that the account is already the right one when the window opens. The alerts continue to arrive in Outlook, where a rule can file them, and the window is where the numbers get read.

The routes, side by side

Route	Window of its own	Sign-in shared with the browser	Requirement
Tab in Chrome or Safari	No	Yes	None
Chrome, install page as app	Yes	Yes, within that Chrome profile	Chrome
Safari, Add to Dock	Yes	No, separate cookie store	macOS Sonoma 14 or later
A site to app tool	Yes, one icon per account	Separate per app	The tool itself

The Chrome route is three clicks. Sign in to Forms, then at the top right choose More, then Cast, save, and share, then Install page as app. Chrome's help notes that installed web apps can include extra capabilities such as offline storage, notifications, file system access, and icon badges, that their settings live behind App info in the window, and that Chrome can start them when the computer is signed in to.

The Safari route needs macOS Sonoma 14 or later. Sign in, choose File, then Add to Dock, and give it a name.

Type the name that you want to use for the web app, then click Add. The web app is saved to the Applications folder of your home folder, and you can also open it from the Dock or Spotlight. Source: support.apple.com

Apple's page lists what can be adjusted afterwards: the name, the URL it opens, the icon, whether navigation controls appear, and whether the title bar takes the site colour. It also notes that a web app can be added as a login item so that it opens automatically at sign-in.

A dedicated tool earns its place when there are several identities to keep apart on one machine, when the icons need to look different at a glance, or when the same layout has to be reproduced on a second Mac without repeating the steps by hand.

Where the time actually goes in a Forms week

Before deciding how much effort this deserves, it helps to look at the shape of the work, because Forms is not used the way a mail client or a design tool is used.

Authoring is a burst. A form gets built in one sitting, usually in half an hour, and then it is finished. Nothing about that sitting is improved much by a Dock icon, because the tab is already open and in focus.

Distribution is a second burst, and it happens somewhere else. Microsoft's documentation describes sending a form as an email in Outlook, as a message in a Teams group or channel, or through a QR code, among other options. Those handoffs start in Forms and end in another application, which is one reason the Forms tab gets buried right after a form is sent.

Monitoring is where the time leaks. Checking responses happens repeatedly over days or weeks, in short visits, usually prompted by an email notification. Each of those visits is the thing an icon actually shortens. A minute spent finding the right tab, plus an occasional wrong account, repeated across a two week collection window, adds up to more than the form took to build.

Analysis is a burst again, and it often leaves Forms entirely, since results can be exported to Excel for further work or grading. That is worth keeping in mind when choosing which window to build. If the real destination is a spreadsheet, the icon that matters may be the one that opens the response view long enough to trigger the export.

Read together, these four phases explain why the advice differs from the usual advice about desktop apps. The argument for an icon is not that Forms is used all day. It is that Forms is checked often, briefly, at unpredictable moments, and those are exactly the visits that a buried tab makes expensive.

Pointing the window at the right page

One detail decides whether the icon saves time or merely relocates the problem: which page it opens.

Opening the Forms home page shows the list of recent forms, which suits an author juggling several at once. Opening a specific form's response view suits the opposite case, a single survey being watched closely for a fortnight. Microsoft's documentation describes that view as the Responses Overview, showing the number of responses and the average time taken to complete the form, with per question response counts below. For a campaign that matters, an icon that opens straight to those numbers removes three clicks from every check.

The URL for a specific form is long and carries an identifier, so capture it from the address bar while the response view is open rather than retyping it. Since the URL of a web app can be changed later in its settings, one icon can be repointed when a project ends instead of being rebuilt.

Teams is the other place Forms already lives, and it is worth deciding deliberately. Forms can be added as a tab in a Teams channel so a group sees results in context. If a team already works that way, a separate icon may duplicate something that is one click away in an application that is open anyway. The icon earns its keep for authoring and for cross tenant work, not for sharing.

What to change first

Sign in to forms.office.com in the browser that will host the window, confirm the account is the one that owns the forms that matter, and build a single icon from that signed in page. Turn on the email notification setting for the form currently collecting responses, since that is the channel that actually alerts. If a second account has to stay signed in as well, a site to app tool keeps the two sessions apart with an icon each, and the supported services list shows which other Microsoft 365 pages people keep in the Dock alongside it.