To deploy a Ping Identity agent from Google Cloud Marketplace, choose the agent that fits the task, select the intended Google Cloud project, verify your Marketplace permissions, then follow that agent listing’s current purchase or deployment flow and accept its terms. Google documents this general process, but the public announcement and Marketplace guidance do not specify the exact button, form fields, tenant connection, or post-subscription setup for each Ping agent. Check the live listing and its onboarding instructions for those details.
Which Ping Identity agent should you choose?
Ping announced three agents for Google Cloud Gemini Enterprise, built using Google’s Agent Development Kit. They cover different identity tasks; they are not described as VM security agents to install on Compute Engine instances.
As an Amazon Associate I earn from qualifying purchases.
| Agent | Intended user and tasks | Documented control |
|---|---|---|
| PingID Device Management Agent | Signed-in employees can pair a replacement phone, list registered devices, rename a device, set one as the default, or remove an old device. | Ping says it has no standing credentials and cannot access resources or act without direction from an authenticated user. |
| PingOne Advanced Identity Cloud Administrator Agent | Administrators can work with users, access, and sessions; examples include password resets, MFA enrollment management, and reviewing user activity. | Only approved operators can access the Advanced Identity Cloud implementation, and the agent requires explicit confirmation before taking action there. |
| PingOne Administrator Agent | Supports administrator work involving users, access, and sessions, including the examples above under assigned access controls and administrative permissions. | Ping describes assigned access controls and administrative permissions. The cited material does not establish the same explicit-confirmation detail for this agent as for the Advanced Identity Cloud agent. |
Ping describes natural-language requests mapped to defined identity actions through Ping APIs. The actions available depend on the authority established for the use case and user; the agents should not be treated as unrestricted or autonomous account access. See Ping’s September 29, 2026 announcement and its descriptions of the PingID agent and administrator agents.
How to deploy an agent through Google Cloud Marketplace
- Choose the agent. Match the listing to the task: employee PingID device self-service, PingOne administration, or Advanced Identity Cloud administration.
- Select the right project and check access. In the Google Cloud console, confirm that the active project is the one intended for the Marketplace transaction. Verify that your account has the IAM roles needed to purchase or deploy the product. Google’s general instructions do not enumerate agent-specific roles.
- Open and review the agent’s listing. Read the product details and any pricing information shown on that live listing. Review the applicable terms before proceeding.
- Use the action shown for that product. Marketplace action labels vary by product type: Google documents examples such as “Subscribe” or “View all plans” for SaaS products and “Launch” or “Get” for VM products. Do not assume which label a Ping agent uses; follow the live listing.
- Complete the prompts and accept the terms. Provide any information requested by the flow and accept the terms presented to finish the Marketplace transaction.
- Follow the listing’s onboarding instructions. Use the agent-specific directions for any tenant connection, permissions configuration, or setup after the transaction. The reviewed public announcement and Google’s general Marketplace procedure do not document those Ping-specific steps.
Google’s instructions for obtaining products are in Get products from Google Cloud Marketplace. The terms presented in the transaction flow are the terms to review and accept for that purchase or deployment.
#1 Best Overall
Do not use the Compute Engine security-agent procedure
Google’s separate Deploying security software agents guide covers installing security software agents on Compute Engine VMs through OS Configuration Management and guest policies. That workflow involves OS Config setup and permissions, project metadata, VM selection, and a deployment bucket. Ping describes the three agents here as conversational agents for Gemini Enterprise; the cited material does not direct administrators to install them on VMs using that security-agent process.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to confirm before and after the Marketplace transaction
- Confirm the agent name and identity environment match the intended task.
- Check the active Google Cloud project and your Marketplace purchase or deployment permissions before starting.
- Read the live listing’s product details, current terms, and any onboarding directions; do not infer a button label or setup fields from another product type.
- For administrative use, confirm that the relevant users or operators have the intended Ping permissions. Ping’s descriptions tie actions to assigned authority, and the Advanced Identity Cloud confirmation requirement applies specifically to changes in that implementation.
Ping Identity’s “Ping Identity + Google Cloud” page is available at pingidentity.com.
Quick Recap
Rank #4
- Wireless iOS device printing (Apple Air Print)
- Wireless Android device and Chromebook printing (Google Cloud Print)
- No need to download and install separate app
- Network (wired/wireless) and USB printer support, Refer user manual below
- No iOS/Android client/device license fees required
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
