No. In general, your pipeline definition file will have several stages; the most common ones being build (build the code into artifacts that can be published onto already deployed infrastructure), test (test the code you just built), deploy (create the infrastructure in the cloud), publish (copy your built artifacts to the infrastructure in the cloud). The ARM/Bicep template is the definition of the infratructure that you are going to deploy.
Once you have the pipeline definition, you can make a dev pipeline, qa pipeline, and prod pipeline (depending on needs) which may run manually or on a specific branch. For example, I keep a "prod" branch that is "the deployed code". When I merge the main branch to prod, it automatically runs my pipeline, which includes running the az deployment group create step (which deploys the infrastructure described by the bicep template).