[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GYEVAADQ72JR19SNC6M71D":3,"skill-same:01M6GYEVAADQ72JR19SNC6M71D":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6GYEVAADQ72JR19SNC6M71D","implementing-google-workspace-sso-configuration",null,"Configure SAML 2.0 single sign-on for Google Workspace with a third-party identity provider, enabling centralized authentication and enforcing organization-wide access policies.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"google workspace","implementing","configuration","workspace","implementing google workspace sso configuration","sso","google","federation","Google-Workspace","identity-provider","saml","access","configure","authentication","provider","cybersecurity","organization","sign","with","wide","2026-11-10 10:12:30",false,"---\nname: implementing-google-workspace-sso-configuration\ndescription: Configure SAML 2.0 single sign-on for Google Workspace with a third-party identity provider, enabling centralized authentication and enforcing organization-wide access policies.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags: [google-workspace, sso, saml, identity-provider, authentication, federation]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Implementing Google Workspace SSO Configuration\n\n## Overview\n\nSingle Sign-On (SSO) for Google Workspace allows organizations to authenticate users through their existing identity provider (IdP) such as Okta, Azure AD (Microsoft Entra ID), or ADFS, rather than managing separate Google passwords. This is implemented using SAML 2.0 protocol where Google Workspace acts as the Service Provider (SP) and the organization's IdP handles authentication. SSO centralizes credential management, enforces MFA policies at the IdP, and enables immediate access revocation when users leave the organization.\n\n\n## When to Use\n\n- When deploying or configuring implementing google workspace sso configuration capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Google Workspace Business, Enterprise, or Education edition\n- Super Admin access to Google Admin Console\n- Identity Provider with SAML 2.0 support (Okta, Azure AD, ADFS, Ping Identity)\n- IdP signing certificate (X.509 PEM format, RSA or DSA)\n- DNS verification for the Google Workspace domain\n\n## Core Concepts\n\n### SAML 2.0 SSO Flow\n\n```\nUser navigates to Google Workspace app (Gmail, Drive, etc.)\n        │\n        ├── Google checks: Is SSO configured for this domain?\n        │\n        ├── YES → Redirect user to IdP Sign-In Page URL\n        │          (SAML AuthnRequest sent via browser redirect)\n        │\n        ├── User authenticates at IdP (credentials + MFA)\n        │\n        ├── IdP generates SAML Response with signed assertion\n        │\n        ├── Browser POSTs SAML Response to Google ACS URL:\n        │   https:\u002F\u002Fwww.google.com\u002Fa\u002F{domain}\u002Facs\n        │\n        ├── Google validates SAML signature against uploaded certificate\n        │\n        └── User is granted access to Google Workspace\n```\n\n### Key SAML Parameters\n\n| Parameter | Value |\n|-----------|-------|\n| ACS URL | `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs` |\n| Entity ID | `google.com\u002Fa\u002F{your-domain}` or `google.com` |\n| NameID Format | `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` |\n| NameID Value | User's primary Google Workspace email |\n| Binding | HTTP-POST (for ACS), HTTP-Redirect (for SSO URL) |\n\n## Workflow\n\n### Step 1: Prepare the Identity Provider\n\n**For Okta:**\n1. Navigate to Applications > Add Application > Search \"Google Workspace\"\n2. Configure the Google Workspace app with your domain\n3. Assign users\u002Fgroups to the application\n4. Download the IdP metadata or note: SSO URL, Entity ID, Certificate\n\n**For Azure AD (Microsoft Entra ID):**\n1. Navigate to Enterprise Applications > New Application > Google Cloud\u002FWorkspace\n2. Configure Single sign-on > SAML\n3. Set Basic SAML Configuration:\n   - Identifier (Entity ID): `google.com`\n   - Reply URL (ACS): `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs`\n   - Sign on URL: `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002FServiceLogin`\n4. Download Federation Metadata XML or Certificate (Base64)\n\n**For ADFS:**\n1. Add Relying Party Trust using federation metadata\n2. Configure claim rules to pass NameID as email address\n3. Export the token-signing certificate\n\n### Step 2: Configure Google Workspace SSO\n\n1. Sign in to Google Admin Console (admin.google.com) as Super Admin\n2. Navigate to Security > Authentication > SSO with third-party IdP\n3. Click \"Add SSO profile\" or configure the default profile\n\n**Third-Party SSO Profile Settings:**\n\n| Setting | Value |\n|---------|-------|\n| Set up SSO with third-party IdP | Enabled |\n| Sign-in page URL | IdP's SAML SSO endpoint (e.g., `https:\u002F\u002Fidp.example.com\u002Fsso\u002Fsaml`) |\n| Sign-out page URL | IdP's logout URL (e.g., `https:\u002F\u002Fidp.example.com\u002Fslo`) |\n| Change password URL | IdP's password change URL |\n| Verification certificate | Upload IdP's X.509 signing certificate |\n| Use a domain-specific issuer | Enabled (uses `google.com\u002Fa\u002F{domain}` as entity ID) |\n\n### Step 3: Assign SSO Profile to Users\n\nSSO profiles can be applied at different scopes:\n\n```\nOrganization-wide (all users)\n    │\n    ├── Org Unit level (specific departments)\n    │   ├── Engineering OU → SSO via Okta\n    │   ├── Marketing OU → SSO via Azure AD\n    │   └── Contractors OU → SSO via specific IdP\n    │\n    └── Group level (specific security groups)\n        └── VPN Users → SSO with additional MFA\n```\n\n1. Navigate to Security > Authentication > SSO with third-party IdP\n2. Select the SSO profile to assign\n3. Choose organizational units or groups\n4. Save and wait for propagation (up to 24 hours, typically minutes)\n\n### Step 4: Configure Network Masks (Optional)\n\nNetwork masks control when SSO is enforced based on the user's IP:\n\n- If the user's IP matches a network mask, they use Google's sign-in page\n- If the user's IP does NOT match, they are redirected to the IdP\n\nThis is useful for allowing direct Google login from corporate network while enforcing SSO for external access.\n\n### Step 5: Test SSO\n\n1. Open an incognito browser window\n2. Navigate to `https:\u002F\u002Fmail.google.com\u002Fa\u002F{your-domain}`\n3. Verify redirect to IdP sign-in page\n4. Authenticate at the IdP\n5. Verify successful redirect back to Google Workspace\n6. Test sign-out flow redirects to IdP logout page\n7. Test with user not assigned in IdP (should fail)\n\n## Validation Checklist\n\n- [ ] IdP SAML application configured with correct ACS URL and Entity ID\n- [ ] IdP signing certificate uploaded to Google Admin Console\n- [ ] SSO profile assigned to target organizational units\u002Fgroups\n- [ ] SAML assertion includes correct NameID (email format)\n- [ ] MFA enforced at IdP for all Google Workspace users\n- [ ] Sign-out URL configured to terminate IdP session\n- [ ] Network masks configured if internal\u002Fexternal access differs\n- [ ] Break-glass Super Admin accounts bypass SSO (use Google auth)\n- [ ] SSO tested with multiple user types (admin, standard, contractor)\n- [ ] SAML response signature validated successfully\n- [ ] Error handling tested (expired cert, invalid user, clock skew)\n\n## References\n\n- [Google Workspace SSO Configuration Guide](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F12032922)\n- [Set Up Custom SAML App - Google](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F6087519)\n- [Okta Google Workspace SAML Guide](https:\u002F\u002Fsaml-doc.okta.com\u002FSAML_Docs\u002FHow-to-Enable-SAML-2.0-in-Google-Apps.html)\n- [SAML 2.0 Technical Overview - OASIS](https:\u002F\u002Fdocs.oasis-open.org\u002Fsecurity\u002Fsaml\u002FPost2.0\u002Fsstc-saml-tech-overview-2.0.html)\n","# Implementing Google Workspace SSO Configuration\n\n## Overview\n\nSingle Sign-On (SSO) for Google Workspace allows organizations to authenticate users through their existing identity provider (IdP) such as Okta, Azure AD (Microsoft Entra ID), or ADFS, rather than managing separate Google passwords. This is implemented using SAML 2.0 protocol where Google Workspace acts as the Service Provider (SP) and the organization's IdP handles authentication. SSO centralizes credential management, enforces MFA policies at the IdP, and enables immediate access revocation when users leave the organization.\n\n\n## When to Use\n\n- When deploying or configuring implementing google workspace sso configuration capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Google Workspace Business, Enterprise, or Education edition\n- Super Admin access to Google Admin Console\n- Identity Provider with SAML 2.0 support (Okta, Azure AD, ADFS, Ping Identity)\n- IdP signing certificate (X.509 PEM format, RSA or DSA)\n- DNS verification for the Google Workspace domain\n\n## Core Concepts\n\n### SAML 2.0 SSO Flow\n\n```\nUser navigates to Google Workspace app (Gmail, Drive, etc.)\n        │\n        ├── Google checks: Is SSO configured for this domain?\n        │\n        ├── YES → Redirect user to IdP Sign-In Page URL\n        │          (SAML AuthnRequest sent via browser redirect)\n        │\n        ├── User authenticates at IdP (credentials + MFA)\n        │\n        ├── IdP generates SAML Response with signed assertion\n        │\n        ├── Browser POSTs SAML Response to Google ACS URL:\n        │   https:\u002F\u002Fwww.google.com\u002Fa\u002F{domain}\u002Facs\n        │\n        ├── Google validates SAML signature against uploaded certificate\n        │\n        └── User is granted access to Google Workspace\n```\n\n### Key SAML Parameters\n\n| Parameter | Value |\n|-----------|-------|\n| ACS URL | `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs` |\n| Entity ID | `google.com\u002Fa\u002F{your-domain}` or `google.com` |\n| NameID Format | `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` |\n| NameID Value | User's primary Google Workspace email |\n| Binding | HTTP-POST (for ACS), HTTP-Redirect (for SSO URL) |\n\n## Workflow\n\n### Step 1: Prepare the Identity Provider\n\n**For Okta:**\n1. Navigate to Applications > Add Application > Search \"Google Workspace\"\n2. Configure the Google Workspace app with your domain\n3. Assign users\u002Fgroups to the application\n4. Download the IdP metadata or note: SSO URL, Entity ID, Certificate\n\n**For Azure AD (Microsoft Entra ID):**\n1. Navigate to Enterprise Applications > New Application > Google Cloud\u002FWorkspace\n2. Configure Single sign-on > SAML\n3. Set Basic SAML Configuration:\n   - Identifier (Entity ID): `google.com`\n   - Reply URL (ACS): `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs`\n   - Sign on URL: `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002FServiceLogin`\n4. Download Federation Metadata XML or Certificate (Base64)\n\n**For ADFS:**\n1. Add Relying Party Trust using federation metadata\n2. Configure claim rules to pass NameID as email address\n3. Export the token-signing certificate\n\n### Step 2: Configure Google Workspace SSO\n\n1. Sign in to Google Admin Console (admin.google.com) as Super Admin\n2. Navigate to Security > Authentication > SSO with third-party IdP\n3. Click \"Add SSO profile\" or configure the default profile\n\n**Third-Party SSO Profile Settings:**\n\n| Setting | Value |\n|---------|-------|\n| Set up SSO with third-party IdP | Enabled |\n| Sign-in page URL | IdP's SAML SSO endpoint (e.g., `https:\u002F\u002Fidp.example.com\u002Fsso\u002Fsaml`) |\n| Sign-out page URL | IdP's logout URL (e.g., `https:\u002F\u002Fidp.example.com\u002Fslo`) |\n| Change password URL | IdP's password change URL |\n| Verification certificate | Upload IdP's X.509 signing certificate |\n| Use a domain-specific issuer | Enabled (uses `google.com\u002Fa\u002F{domain}` as entity ID) |\n\n### Step 3: Assign SSO Profile to Users\n\nSSO profiles can be applied at different scopes:\n\n```\nOrganization-wide (all users)\n    │\n    ├── Org Unit level (specific departments)\n    │   ├── Engineering OU → SSO via Okta\n    │   ├── Marketing OU → SSO via Azure AD\n    │   └── Contractors OU → SSO via specific IdP\n    │\n    └── Group level (specific security groups)\n        └── VPN Users → SSO with additional MFA\n```\n\n1. Navigate to Security > Authentication > SSO with third-party IdP\n2. Select the SSO profile to assign\n3. Choose organizational units or groups\n4. Save and wait for propagation (up to 24 hours, typically minutes)\n\n### Step 4: Configure Network Masks (Optional)\n\nNetwork masks control when SSO is enforced based on the user's IP:\n\n- If the user's IP matches a network mask, they use Google's sign-in page\n- If the user's IP does NOT match, they are redirected to the IdP\n\nThis is useful for allowing direct Google login from corporate network while enforcing SSO for external access.\n\n### Step 5: Test SSO\n\n1. Open an incognito browser window\n2. Navigate to `https:\u002F\u002Fmail.google.com\u002Fa\u002F{your-domain}`\n3. Verify redirect to IdP sign-in page\n4. Authenticate at the IdP\n5. Verify successful redirect back to Google Workspace\n6. Test sign-out flow redirects to IdP logout page\n7. Test with user not assigned in IdP (should fail)\n\n## Validation Checklist\n\n- [ ] IdP SAML application configured with correct ACS URL and Entity ID\n- [ ] IdP signing certificate uploaded to Google Admin Console\n- [ ] SSO profile assigned to target organizational units\u002Fgroups\n- [ ] SAML assertion includes correct NameID (email format)\n- [ ] MFA enforced at IdP for all Google Workspace users\n- [ ] Sign-out URL configured to terminate IdP session\n- [ ] Network masks configured if internal\u002Fexternal access differs\n- [ ] Break-glass Super Admin accounts bypass SSO (use Google auth)\n- [ ] SSO tested with multiple user types (admin, standard, contractor)\n- [ ] SAML response signature validated successfully\n- [ ] Error handling tested (expired cert, invalid user, clock skew)\n\n## References\n\n- [Google Workspace SSO Configuration Guide](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F12032922)\n- [Set Up Custom SAML App - Google](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F6087519)\n- [Okta Google Workspace SAML Guide](https:\u002F\u002Fsaml-doc.okta.com\u002FSAML_Docs\u002FHow-to-Enable-SAML-2.0-in-Google-Apps.html)\n- [SAML 2.0 Technical Overview - OASIS](https:\u002F\u002Fdocs.oasis-open.org\u002Fsecurity\u002Fsaml\u002FPost2.0\u002Fsstc-saml-tech-overview-2.0.html)\n",{"name":5,"tags":43,"author":45,"domain":33,"license":14,"version":46,"subdomain":47,"description":7},[44,23,28,27,31,25],"google-workspace","mahipal","1.0","identity-access-management","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill implementing-google-workspace-sso-configuration",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill implementing-google-workspace-sso-configuration",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill implementing-google-workspace-sso-configuration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002FSKILL.md",true,[69,75,80,86,90,94,100],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Ftemplate.md","ASSET","资产文件",1320,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Fassets\u002Ftemplate.md",{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002FLICENSE",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",1858,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fstandards.md",1421,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Freferences\u002Fstandards.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fworkflows.md",3935,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Freferences\u002Fworkflows.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fagent.py","SCRIPT","脚本",7022,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Fscripts\u002Fagent.py",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fprocess.py",8282,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Fscripts\u002Fprocess.py",[105,142,171,191,211,236],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":122,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[112,117],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[123,124,125,126,31,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"architecture","azure","azure apim architecture","component","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":156,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[148,149,152,155],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},{"categoryNo":150,"categoryName":151,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":153,"categoryName":154,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[157,158,159,160,124,161,162,163,164,165,166,167,131,132,138,168,169,139,170,19],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[177],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[179,180,181,182,124,31,131,132,29,183,184,185,186,187,188,139,189,190,19,141],"policy","authoring","apim policy authoring","security","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":199,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[197,198],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[200,182,201,131,185,202,124,157,203,204,205,206,132,207,139,208,209,210,140,141],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[218,219,220,159,221,222,223,224,131,225,226,227,228,229,230,231,232,233,234,235],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":242,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[238,243,244,245,246,247,248,183,249,250],"npm","js","calculate","node","math","user","compute","errors"]