Exchange Connection Problems

Fix Exchange Object Reference Errors When Adding Delegates

Tauseeq MagsiTauseeq Magsi Oct 29, 2026 869 views

Question details

The user needs to resolve an object reference error that appears when trying to assign Send As permissions for a distribution group.

Fix Exchange Object Reference Errors When Adding Delegates
Product
Microsoft Exchange
Device & OS
not provided
Scenario
Assigning Send As permissions to a specific user for a distribution group in Exchange.
Observed behavior
Exchange displays an 'object reference not set to an instance of an object' error instead of applying the requested delegate permission.
Before you start

Ensure you have administrator access to your Exchange Online environment and that the Exchange Online PowerShell module is installed on your machine.

Solution 1Recommended

Assign Send As Permission Using Exchange Online PowerShell

Bypassing the Exchange Admin Center GUI and using PowerShell directly often resolves web-based object reference errors.

Object reference errors in the Exchange Admin Center are often caused by temporary web interface glitches or browser cache issues. Using PowerShell allows you to apply the permissions directly to the backend servers.

1
Connect to Exchange Online

Open PowerShell as an administrator and run the Connect-ExchangeOnline cmdlet. Log in using your global administrator or Exchange administrator credentials.

2
Run the Add-RecipientPermission Command

Execute the following command, replacing the placeholders with your actual data: Add-RecipientPermission -Identity "GroupEmailAddress" -Trustee "UserEmailAddress" -AccessRights SendAs

3
Verify the Permission

To ensure the permission was added successfully, run Get-RecipientPermission -Identity "GroupEmailAddress". The user should now be listed with SendAs rights.

Assign Send As Permission Using Exchange Online PowerShell
Advanced Troubleshooting: If the PowerShell command also fails, use Get-DistributionGroup to check if the group or user account is synchronized from an on-premises Active Directory. Synchronized objects must be managed locally.
Free Microsoft Office alternative

Need a Reliable Alternative for Office Documents? Try WPS Office

While resolving Exchange server errors requires specific administrative tools, your daily document creation shouldn't rely on costly and heavy Office subscriptions. WPS Office provides a lightweight, feature-rich suite that serves as the perfect alternative.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your PC or Mac.
  2. 2. Install WPS Office: Run the downloaded setup file and follow the straightforward on-screen instructions to install the software.
  3. 3. Open Your Files: Launch WPS Office to easily open, edit, and save your existing Word, Excel, and PowerPoint documents without losing any formatting.
Fully compatible with all major Microsoft Office file formats (.docx, .xlsx, .pptx).Free to use, significantly lowering your software licensing costs.Lightweight architecture ensures fast installation and smooth operation on any device.Familiar tabbed user interface guarantees a seamless transition with zero learning curve.
microsoft office alternative - wps office

Frequently Asked Questions

Why do object reference errors happen in the Exchange Admin Center?

These errors usually occur due to browser caching issues, temporary Azure AD synchronization delays, or bugs within the Exchange Admin Center web interface. PowerShell provides a more direct communication method with the server, circumventing these UI problems.

Can I manage Send As permissions for groups synced from on-premises AD?

If a distribution group is cloud-managed, you can update permissions in Exchange Online. However, if the group is synchronized from an on-premises Active Directory via Azure AD Connect, you must manage its permissions in your local AD environment.

How long does it take for Send As permissions to become active?

Once assigned successfully, Send As permissions can take anywhere from 15 minutes to 24 hours to fully propagate across Exchange servers and update the Offline Address Book (OAB) in the Outlook desktop client.