Solve the New Outlook problem – and unlock the full Microsoft 365 platform
Bring the power of Microsoft Graph to VBA
VBAuth provides a modern, supported authentication layer for VBA applications working with Microsoft 365.

Yes – This Fixes the “New Outlook” Problem
When Microsoft introduced “New Outlook” for Windows, traditional COM automation stopped working.
For Access and Excel developers who relied on:
- Outlook.Application
- Application.CreateItem
- MailItem.Send
- Any form of Calendar automation via the Outlook Object Model
…the "upgrade" broke existing solutions.
VBAuth replaces that approach with direct Microsoft Graph API calls.
Instead of automating Outlook itself, your VBA code communicates securely with Microsoft 365 using:
- OAuth 2.0 authentication
- Microsoft Graph endpoints
- Full support for Modern Authentication and MFA
- A supported, forward-looking architecture
Not a "workaround". Not a "kludge".
A modern replacement.
But This Is Bigger Than Outlook
This Isn’t Just About Email
Solving the Outlook issue is often the starting point.
But VBAuth enables your VBA application to interact with the entire Microsoft 365 ecosystem through Microsoft Graph.
With VBAuth, your application can:
- Send and read email
- Create, update, and query calendar appointments
- Create Teams meetings
- Retrieve Teams call information
- Access SharePoint document libraries
- Manage OneDrive files
- Query User and Group information
- Work with any endpoint your tenant permits
If Microsoft exposes it through Graph, your VBA code can reach it.
VBAuth turns legacy VBA solutions into modern Microsoft 365 applications – without rewriting them in .NET.
Designed for Professional VBA Developers
A Simple, Clear Developer Experience
VBAuth does not abstract Microsoft Graph into a black box.
It provides secure authentication and token management, allowing you to work directly with Graph in a controlled and explicit way.
A typical email send from VBA becomes:
Private Sub SendEmail()
Dim strPayload As String
Dim strEmailResult As String
Dim strTo As String
Dim strSubject As String
Dim strBody As String
Dim strErrors As String
strTo = "bob@example.com"
strSubject = "This email is sent from VBA using Graph"
strBody = "I can send any content – including rich HTML content – in this way."
strErrors = ""
strPayload = BuildSendMailPayload( _
strTo:=strTo, _
strSubject:=strSubject, _
strBody:=strBody, _
blnSaveToSentItems:= True)
If SendEmail(strPayload, strEmailResult) Then
MsgBox "Email sent successfully.", vbInformation, "Send Email"
Else
MsgBox "Failed to send email." & vbCrLf & vbCrLf & strEmailResult, _
vbCritical, "Send Email"
End If
End Sub
No COM automation.
No deprecated interfaces.
No stored passwords
You authenticate once, VBA obtains a secure access token, and your code works directly with Microsoft’s supported API.
Full documentation and code samples are provided.
Built the Way Microsoft Intends
Secure. Supported. Compliant.
VBAuth follows Microsoft’s recommended authentication model.
- Uses official OAuth flows
- Supports multi-factor authentication
- Respects tenant security policies
- Requires Azure App registration
- No embedded credentials
- No insecure legacy authentication
- No hidden telemetry
- No "calling home"
VBAuth does not transmit usage data or application data outside your tenant.
Licensing validation is performed locally and does not require continuous internet verification.
This is not a hack around security restrictions.
It is an implementation aligned with Microsoft’s direction for Microsoft 365 development.
Built for modern VBA Solutions
Who is this tool for?
VBAuth is designed for:
- Access developers maintaining enterprise systems
- Excel-based business applications
- Organisations migrating fully to Microsoft 365
- Developers modernising legacy automation
- Consultants delivering tenant-aware Microsoft 365 integrations
If you are building or maintaining professional VBA solutions in a Microsoft 365 environment, VBAuth provides the authentication layer Microsoft now requires.
Documentation and Transparency
Fully Documented. Technically Transparent.
The complete documentation includes:
- Detailed setup guides
- Azure App Registration instructions
- Security architecture explanations
- Fully working code samples for over 20 Microsoft Graph operations — mail, calendar, contacts, Teams and much more
- Admin and developer tooling samples — Entra ID app and role management, plus comprehensive auditing
- Token management guidance
- Deployment considerations
- Licensing explanations
Note that for the first time, the full Graph API surface is fully accessible from VB — with many hundreds of operations now available
Licencing
VBAuth uses a two-tier licensing model.
Developer licence
For development, deployment within your own tenant and internal testing.
Choose your pricing model:
- £195 per year
- £695 lifetime licence
Required for each development tenant, regardless of how many developers use the product.
Deployment licence
For production use within a tenant
- £995 lifetime licence
- Required per Microsoft 365 tenant
A Deployment Licence permits use of VBAuth within that tenant’s live environment. A current developer license is also required for the purchase of any deployment licenses.
Special offer: When you sign up for a Developer Licence, we will give you a 50% discount on your first three deployment licences.
Definition of "Lifetime"
“Lifetime” refers to the lifetime of the current major Microsoft Graph API release.
Should Microsoft introduce a breaking major version change to the Graph API, a future major release of VBAuth may require an upgrade.
Modern Authentication for VBA
Microsoft 365 has moved to OAuth and Microsoft Graph.
VBAuth enables VBA to move with it.