How to Use Microsoft Access on a Mac with an M1 Processor
Question details
The user needs to know how to install and run Microsoft Access on a Mac computer equipped with an Apple M1 processor.

- Product
- Microsoft Access
- Device & OS
- Mac (Apple Silicon / M1)
- Scenario
- Running a Windows-exclusive database application on a Mac computer with Apple silicon architecture.
- Observed behavior
- Microsoft Access does not have a native macOS release and cannot be installed directly, requiring a Windows environment workaround to function on Apple's M1 hardware.
Ensure your Mac has sufficient disk space (at least 20GB free) and memory to allocate to a virtual machine. You will also need a valid Microsoft 365 subscription that includes Access and a license for Windows 11.
Use Parallels Desktop to Run Windows on M1 Mac
Parallels Desktop is virtualization software optimized for Apple silicon, allowing you to install a Windows 11 ARM environment where you can seamlessly run Microsoft Access.
Because Apple silicon uses an ARM architecture, traditional x86/x64 Windows versions cannot run via Boot Camp. Parallels Desktop automates the installation of Windows 11 on ARM, which features built-in emulation to run x64 applications like Microsoft Access with near-native performance.
Download and install Parallels Desktop for Mac from the official website. Open the application and grant it the necessary macOS system permissions.
Launch Parallels Desktop to trigger the Installation Assistant. Click 'Get Windows 11 from Microsoft' and select 'Install'. Parallels will automatically download and configure the correct ARM version of Windows.
Once the Windows virtual desktop loads, open the Microsoft Edge browser inside Windows and navigate to office.com. Sign in with the Microsoft account associated with your subscription.
Click the 'Install apps' button on your Microsoft 365 dashboard to download the Office setup file. Run the installer to load the suite, including Access, into your Windows virtual machine.
Open the Windows Start Menu, type 'Access', and click the Microsoft Access application icon to begin managing your databases.

Use a Cloud PC Service like Windows 365
If you do not want to allocate local system resources to a virtual machine, you can stream a full Windows desktop containing Microsoft Access from the cloud.
Try WPS Office for Native Apple Silicon Support
While Microsoft Access requires virtualization to run on a Mac, WPS Office provides a fully native, lightning-fast experience for your standard document, spreadsheet, and presentation needs on M1, M2, and M3 Macs without needing a virtual machine.
- 1. Download for Mac: Visit the WPS Office website and download the Mac version, which automatically detects your Apple silicon architecture.
- 2. Install the Application: Open the downloaded .dmg file and drag the WPS Office icon into your Applications folder.
- 3. Start Creating: Launch WPS Office natively from your Launchpad to instantly create or edit Office-compatible files without running Windows.

Frequently Asked Questions
Will Microsoft ever release a native version of Access for macOS?
Currently, Microsoft has announced no plans to release a native macOS version of Access. The application remains highly dependent on Windows-specific technologies, making virtualization the only viable solution for Mac users.
Can I use Apple's Boot Camp to install Windows on an M1 Mac?
No, Boot Camp Assistant is not supported on Macs with Apple silicon (M1, M2, M3). You must use virtualization software like Parallels Desktop or VMware Fusion to run Windows on these devices.
Is Microsoft Access slow when running through Parallels on an M1 chip?
For most database management tasks, Microsoft Access runs exceptionally well via Parallels on an M1 Mac. Windows 11 on ARM includes efficient x64 emulation, and Parallels is highly optimized to utilize the M1 chip's performance capabilities.
Does CrossOver Mac support Microsoft Access?
While CrossOver allows many Windows applications to run on Mac without a full Windows OS, Microsoft Access relies on complex database drivers and integrations that often do not function correctly in CrossOver. A full virtual machine like Parallels is highly recommended for stability.




