Required Scopes and Endpoint Domains for Google Calendar

When integrating with Google Calendar, your application needs specific permissions to interact with the API.

These permissions are defined by access scopes, which determine what data your application can access and what actions it can perform.

This topic provides information about the required access scopes and endpoint domains for the Google Calendar cmdlet.

Understanding Scopes

Scopes are a way to limit an application's access to a user's data. They define the specific actions that an application can perform on behalf of the user.

For example, a read-only scope might allow an application to view data, while a full access scope might allow it to modify data.

Required Scopes for Google Calendar

Scope	Description
googleapis.com/auth/calendar	While Google Calendar provides read-only scopes, the driver only surfaces the full one. This scope is required for full access to read and write permissions.
googleapis.com/auth/calendar.events	This scope is required for read-only access.

Understanding Endpoint Domains

Endpoint domains are the specific URLs that the application needs to communicate with in order to authenticate, retrieve records, and perform other essential operations.

Allowlisting these domains ensures that the network traffic between your application and the API is not blocked by firewalls or security settings.

Note: Most users do not need to make any special configurations. Allowlisting is typically only necessary for environments with strict security measures, such as restricted outbound network traffic.

Required Endpoint Domains for Google Calendar

Domain	Always Required	Description
accounts.google.com	TRUE	The subdomain used for OAuth.
googleapis.com	TRUE	The domain used for accessing various services.