New Outlook Custom Forms Gap for Classic Outlook Users: Alternatives

Classic Outlook users who rely on custom forms to standardize data entry, automate workflows, or enforce business rules will find that the new Outlook for Windows does not support custom forms. This gap affects tasks such as incident tracking, approval requests, and structured email templates that were built using the Outlook Forms Designer. This article explains why custom forms are missing in new Outlook, lists the specific features that will not migrate, and provides three practical alternatives to regain similar functionality. By the end, you will know how to adapt your processes without losing productivity.

Why Custom Forms Do Not Work in New Outlook

Custom forms in Classic Outlook are built using the Outlook Forms Designer, which relies on the COM-based VBScript engine and the Outlook Object Model. These forms are stored as .ofs files or published directly to a folder or the Organizational Forms Library. The new Outlook for Windows is a web-based application that uses the Microsoft 365 web platform. It does not include the COM infrastructure needed to load or execute VBScript code. As a result, any form that uses custom fields, validation rules, or automated actions will not open in new Outlook. The form either fails to load or displays a generic message that the form is unavailable.

Microsoft has confirmed that custom forms are not on the roadmap for new Outlook. The company instead recommends using modern alternatives such as Microsoft Forms, Power Automate, and SharePoint lists. Users who must keep custom forms should stay on Classic Outlook until their organization completes a migration plan.

Specific Features That Will Not Migrate

The following custom form elements are lost when switching to new Outlook:

• Custom field definitions (text, number, date, dropdown) added via the Forms Designer.
• VBScript event handlers such as Item_Open, Item_Send, or Item_Close.
• Custom action buttons and menu items defined in the form.
• Published forms in the Organizational Forms Library or folder-level forms.
• Form regions and add-in components that extend the standard form layout.

Three Alternatives to Custom Forms in New Outlook

Each alternative replaces a specific use case that custom forms previously handled. Choose the method that matches your original workflow.

1. Microsoft Forms for Data Collection and Surveys

Use Microsoft Forms when you need a structured input form that collects responses into a spreadsheet. This replaces custom forms used for incident reports, feedback requests, or order forms.

1. Open Microsoft Forms
   Go to forms.office.com and sign in with your work or school account.
2. Create a new form
   Click New Form and give it a title such as Incident Report. Add questions using the Choice, Text, Date, or Rating options.
3. Add branching logic if needed
   Select a question, click the three dots, and choose Add branching. Redirect respondents to different sections based on their answer.
4. Share the form link
   Click Collect responses, copy the link, and paste it into a new Outlook email. Recipients complete the form in their browser.
5. View responses
   Open the Responses tab in Microsoft Forms to see individual answers or export them to Excel.

Microsoft Forms does not run inside the Outlook window. Users click a link to open the form in a browser. This is the closest replacement for a custom form that enforces field structure.

2. Power Automate for Automated Workflows

Use Power Automate when your custom form used VBScript to send approval requests, update a SharePoint list, or send an automatic reply. Power Automate triggers run on new Outlook email events without needing custom code.

1. Open Power Automate
   Go to make.powerautomate.com and sign in with your Microsoft 365 account.
2. Create an automated flow
   Click Create and select Automated cloud flow. Choose the trigger When a new email arrives (V3) from the Outlook connector.
3. Set trigger filters
   In the trigger card, set Folder to Inbox. Optionally add a filter such as Subject contains Approval to only process relevant messages.
4. Add an action
   Click New step and search for the action you need. For example, select Send an approval to route the email to a manager, or Create item to save data to a SharePoint list.
5. Test and turn on the flow
   Click Save, then Test. Send yourself a test email that matches the filter. Verify the flow runs correctly, then turn it on permanently.

Power Automate replaces the automation part of custom forms. It cannot display a custom form inside the Outlook reading pane, but it can collect data from a message body or attachment and process it automatically.

3. SharePoint Lists for Structured Data Entry

Use a SharePoint list when your custom form stored data in a folder and required consistent fields such as Priority, Status, or Assigned To. SharePoint lists provide column validation, views, and integration with new Outlook.

1. Create a SharePoint list
   Go to your SharePoint site, click New and select List. Choose Blank list and name it Project Requests.
2. Add columns
   Click Add column and choose Choice, Number, Date and Time, or Person or Group. For example, add a column named Priority with choices Low, Medium, High.
3. Set column validation
   Select a column, click Column settings, and choose Edit. Under Require that this column contains information, select Yes. For a Choice column, you can also set a default value.
4. Share the list in new Outlook
   In new Outlook, compose a new email. Click the Insert tab and choose SharePoint List. Select the list you created. The list appears as a table in the email body. Recipients can edit the table inline, and changes sync back to SharePoint.
5. Create views for different teams
   In SharePoint, click All Items and choose Save view as new view. Filter by a column such as Assigned To to show only each user’s items.

SharePoint lists replace the data storage and field structure of custom forms. The inline table in new Outlook gives users a form-like experience without leaving the email.

Common Limitations and Workarounds

Custom Forms with VBScript Validation Still Fail

If your custom form used VBScript to check field values before sending, neither Microsoft Forms nor SharePoint lists can replicate that exact behavior. Use Power Automate to add a condition after the form submission. For example, if a field is empty, the flow sends a rejection email instead of processing the entry.

Organizational Forms Library Cannot Be Accessed

Forms published to the Organizational Forms Library in Classic Outlook are not visible in new Outlook. Export the form definition as an .ofs file and keep it archived. Then rebuild the process using one of the three alternatives above. Do not rely on the library for active workflows.

Custom Form Regions and Add-ins Are Blocked

Form regions created with the Add-In Express or similar tools will not load in new Outlook. Check whether the add-in provider offers a web-based version that works in new Outlook. If not, replace the form region with a SharePoint list that has calculated columns or conditional formatting.

Classic Outlook vs New Outlook: Custom Form Support

Item	Classic Outlook	New Outlook
Custom form engine	COM-based VBScript	Not supported
Form Designer tool	Developer tab > Design a Form	Not available
Organizational Forms Library	Published and accessible	Cannot load
VBScript event handlers	Item_Open, Item_Send, Item_Close	No equivalent
Custom field validation	Built into form	Requires Power Automate
Inline data entry in email	Custom form in reading pane	SharePoint inline table
Automated approval workflow	VBScript + rules	Power Automate
External data collection	Custom form sent to external users	Microsoft Forms link

You can now choose the right replacement based on your original custom form use case. Start by identifying whether your form mainly collected data, automated a workflow, or enforced field validation. Then deploy Microsoft Forms, Power Automate, or a SharePoint list accordingly. For complex scenarios that combine all three, chain a Microsoft Form submission to a Power Automate flow that writes to a SharePoint list. This gives you the closest experience to a custom form in new Outlook without losing any critical business logic.