Best Seller Toys

Wednesday, 11 February 2026

[Product Update] Automatic enablement of new OpenTelemetry ingestion API

Posted by Sani P at 00:53

0 comments

project_number,project_id,project_name
93312449343,blogg-1070,blogg

MY CONSOLE

Hello RAMDANI,

You may have previously received a notification regarding this update. If so, please disregard this message.

We're writing to let you know that Cloud Observability has launched a new OpenTelemetry (OTel) ingestion API that supports native OpenTelemetry Protocol (OTLP) logs, trace spans, and metrics.

Starting March 23, 2026, this API will be added as a dependency for the current Cloud Logging, Cloud Trace, and Cloud Monitoring ingestion APIs. This change ensures a seamless transition as collection tools migrate to this new unified endpoint.

What you need to know

Key changes:

The existing Cloud Observability ingestion APIs (logging.googleapis.com, cloudtrace.googleapis.com, and monitoring.googleapis.com) are automatically activated when you create a Google Cloud project using the Google Cloud console or gcloud CLI. The behavior remains unchanged for projects created via API, which do not have these ingestion APIs enabled by default. Starting March 23, 2026, the new OTel ingestion endpoint telemetry.googleapis.com will automatically activate when any of these specified APIs are enabled.
In addition, we will automatically enable this new endpoint for all existing projects that already have current ingestion APIs active.

What you need to do

No action is required from you for this API enablement change, and there will be no disruption to your existing services. You may disable the API at any time by following these instructions.

Refer to the attachment for a list of the projects that will automatically enable the new endpoint.

[Product Update] New security enhancement for your Google Cloud environment

Posted by Sani P at 01:36

0 comments

MY CONSOLE

Hello RAMDANI,

We're reaching out with an important update regarding enhancing the security of sensitive actions in your Google Cloud environment. This update strengthens protection against unauthorized access to your critical Google Cloud resources.

We have provided additional information below to guide you through this change.

What you need to know

Key changes

Starting in July 2025, to further protect your critical Google Cloud resources, you will need to re-enter your password or complete multi-factor authentication (MFA) for certain sensitive actions. These actions include billing assignment changes and IAM policy changes at the Organization, Folder, or Project level.

This additional authentication step ensures that only authorized users can make critical changes to billing and access control settings.

Re-authentication limitations

This re-authentication will initially apply to Google Cloud Console users with Google Cloud Identity. It will not apply to programmatic user account access or external identities federated through Workforce Identity pools and SSO.

Actions that require re-authentication

Specifically, you will be prompted to re-authenticate when performing the following actions (which correspond to these API calls):

resourcemanager.organizations.setIamPolicy
resourcemanager.folders.setIamPolicy
resourcemanager.projects.setIamPolicy
billing.accounts.setIamPolicy
billing.accounts.move
billing.accounts.removeFromOrganization
billing.resourceAssociations.create
billing.resourceAssociations.delete
resourcemanager.projects.deleteBillingAssignment
resourcemanager.projects.createBillingAssignment
resourcemanager.tagValueBindings.delete

Note: Service accounts are not affected by these new re-authentication requirements.

What you need to do

No action is required from you. This enhanced security will be automatically applied starting July 2025.

[Action Required] Mandatory multi-factor authentication for Google Cloud console, gcloud CLI, and Firebase console access

Posted by Sani P at 04:56

0 comments

MY CONSOLE

Hello RAMDANI,

We're writing to inform you that starting May 12, 2025, you will be required to use multi-factor authentication (MFA), also known as 2-Step Verification (2SV), to access Google Cloud console, gcloud CLI, and Firebase console. You're receiving this notice because you have access to projects on Google Cloud.

We understand this change may require some configuration adjustments and have provided additional information below to assist you.

What you need to know

In November 2024, we announced that Google Cloud will be mandating MFA, also known as 2-Step Verification (2SV), for all users. This helps protect your account by requiring both a password and an additional form of verification, such as a phone, security key, or Google Authenticator code, when signing in.

Starting May 12, 2025, 2SV will be mandatory to access Google Cloud console, gcloud CLI, and Firebase console.

What you need to do

To ensure continued access to Google Cloud console, gcloud CLI, and Firebase console, you are required to turn on 2-Step Verification for your account from security.google.com.

Exclusions

Apps and workloads that are hosted on Google Cloud, including those that use Google APIs

Other services, like Google Photos, YouTube, and Google Workspace (including Gmail, Google Sheets, and Google Slides) are not impacted by this requirement