LogoLogo
LogoLogo
  • Welcome
  • Details
  • Editions
  • Use Cases
  • SCEPMAN Deployment
    • Getting Started
      • Standard Guide
      • Extended Guide
    • Permissions
      • Azure App Registration
      • Managed Identities
    • Deployment Options
      • Marketplace deployment
      • Enterprise deployment
      • Terraform deployment
    • Root CA
    • Intermediate CA
  • Certificate Management
    • Revocation
    • Microsoft Intune
      • Windows
        • Certificate Based Authentication for RDP
      • macOS
      • Android
      • iOS/iPadOS
      • Linux
    • Jamf Pro
      • General Configuration
      • Computers
      • Devices
      • Users
    • Other MDM Solutions
      • Google Workspace
        • ChromeOS
      • Kandji
      • Mosyle
      • SOTI MobiControl
    • Certificate Master
      • Manage Certificates
      • Certificate Signing Request (CSR)
      • TLS Server Certificate
      • Sub CA Certificate
      • Code Signing Certificate
      • Client Certificate
      • User Certificate
    • Domain Controller Certificates
    • Enrollment REST API
      • Self Service Enrollment
        • Intune Managed Linux Client
        • Unmanaged Linux Client
      • API Enrollment
        • Linux Server
        • Windows Server
      • SCEPmanClient
  • Azure Configuration
    • Application Insights
    • App Service Sizing
      • Autoscaling
    • Custom Domain
    • Geo-Redundancy
    • Health Check
      • Using 3rd Party Monitoring
    • Log Management
    • Moving Resources
    • Private Endpoints
    • Split-Tenancy
  • Update Strategy
  • SCEPman Configuration
    • SCEPman Settings
      • Basics
      • Certificates
      • Certificate Master
      • CRL
      • Dependencies (Azure Services)
        • Azure KeyVault
        • Logging
        • Microsoft Entra ID (Azure AD)
        • National Cloud Platforms
      • Enrollment REST API
      • OCSP
      • SCEP Endpoints
        • DC Validation
        • Intune Validation
        • Jamf Validation
        • Static Validation
        • Static-AAD Validation
    • Certificate Master Settings
      • Basics
      • Microsoft Entra ID (Azure AD)
      • Logging
      • National Cloud Platforms
    • Application Artifacts
    • Certificate Master RBAC
    • Device Directories
    • Intune Strong Mapping
  • Other
    • Security & Privacy
    • Support
    • Licensing
      • Azure Marketplace
    • FAQs
      • General
      • Certificate Connector
      • Network Access Controllers
      • Renewing SCEPman Root CA
    • Troubleshooting
      • Common Problems
      • Certifried Security Vulnerability
      • Cisco ISE Host Header Limitation
      • Intune service discovery API permissions
      • Re-enrollment trigger
  • Uninstallation
  • Change Log
  • Links
  • SCEPman Website
Powered by GitBook
On this page

Was this helpful?

  1. SCEPMAN Deployment
  2. Deployment Options

Marketplace deployment

Azure Marketplace Deployment

Last updated 1 month ago

Was this helpful?

  • To deploy SCEPman from Azure Marketplace, please visit this .

  • Click Get it now and afterwards Continue. You will be re-directed to the marketplace item on Azure Portal.

  • Click Create.

  • Now, follow these steps to deploy SCEPman in your Azure tenant:

If you have a license key, you can paste it into the field License Key. Leave it empty to use the free Community Edition of SCEPman.

To maximize compatibility, for the Organization Name we recommend to omit

  • language-specific special characters (e.g. ö, ø, é, ...)

  • a leading space (spaces between words can be used)

  • quotation marks

  1. Select an existing resource group or create a new one (SCEPman resources will be deployed in this group)

  2. Set the region according to your preferred data center location. It must match the region of the resource group - in case you have selected an existing one. It will be assigned to the resource group otherwise.

  3. Set an Organization Name. This field is important as the organization provided here will manifest itself in the O= field of the Root CA that is going to be created later on.

  4. Click Review + Create.

  5. Click Create.

Select your preferred Update Channel. By default, the is configured as . This parameter determines from which the binaries for SCEPman will be loaded. For production environments, we recommend to use the Production Channel (default).

Congratulations! The deployment of SCEPman is done. Please continue with the of the to complete the installation of SCEPman.

link
update strategy
channel
Standard Guide
next step
Evergreen approach