While Google has been a long-time supporter of DMARC, there are still a few Google apps that aren't fully equipped to send DMARC-compliant emails under Sender Policy Framework (SPF) guidelines.
If you're using Google Workspace / G-Suite with your own domain, emails sent from certain Google apps (like Docs, Sheets, Slides, Gmail API, and Calendar) will still use a domain that points back to Google, not your domain. This means SPF can't align with your domain and there is a high risk for rejection of those emails.
If your organization’s DMARC policy is set to either P=Quarantine or P=Reject and DKIM isn't properly configured, your emails will fail DMARC checks, and your Google Calendar invites stand a high chance of being blocked.
If DKIM has not already been configured for your domain, please see the partner Knowledge Base article on Configuring DKIM for Google Workspace, located here.
Steps to enable DKIM:
Once configured, giving the domain a couple of days to let traffic and reports come in is best. Once some data has collected, visiting the DMARC Director portal will reflect the new records and will show those emails with DKIM signatures from Google Workspace. These signatures are correctly attached and aligned, ensuring the email meets DMARC standards.
While it is always preferred to achieve full DMARC compliance using both SPF and DKIM, due to the way Google sends Calendar invites and emails from other applications, this isn't possible. At this point in time, using DKIM authentication is the only solution.