Run From Package Mode
Whenever you push changes to the chosen branch, the Function App updates itself automatically using Run From Package.
Last updated
Was this helpful?
Whenever you push changes to the chosen branch, the Function App updates itself automatically using Run From Package.
Last updated
Was this helpful?
Note: If you’re a sponsor using a hosted CIPP instance, you can skip this page—Run From Package is already set for you.
Most Azure Function Apps can be deployed using various methods, but Run From Package is a streamlined, read-only approach that pins your Function App’s code to a zip file. This method:
Ensures consistent deployment (updates happen atomically when the package is replaced).
Makes rollback and troubleshooting simpler.
Often leads to faster cold starts since your code is pre-packaged and ready to go.
If you used our ARM template from the page, your Function App should already be in Run From Package mode, deploying from the latest.zip file. To confirm:
Open Azure Portal → Locate the Function App in your resource group.
Go to Configuration (or Settings → Application Settings, depending on portal version).
Look for an Application Setting named WEBSITE_RUN_FROM_PACKAGE.
It should be set to 1.
If it is, great—your Function App is already running from a package zip.
If you want your Function App to auto-update whenever you commit to your CIPP-API fork, follow these steps:
Still in the Function App settings, go to Deployment Center (sometimes under Deployment → Deployment Center).
If an existing CI/CD connection is configured, Disconnect it to avoid conflicts.
Under Source, select GitHub, then log in if prompted.
Choose your Organization, Repository, and Branch (where your CIPP - code lives).
Leave “Workflow Option” set to “Add a workflow” (the default).
For Authentication Type, pick “Basic Authentication.” (Azure portal doesn’t support Identity-based auth yet.)
Click Add a workflow, then Save.
Repeat this for any additional function apps you may have deployed for .
Your Function App will now be automatically updated pull directly from your GitHub fork whenever you push commits to the selected branch. For day-to-day development, this means less manual deployment and faster iteration on your CIPP-API codebase.
If you run into any snags:
Check the Azure Portal’s Logs under your Function App.
Review your GitHub Actions logs for build/deployment errors.
That’s it! You’re now set up for streamlined, package-based deployments with automatic updates.