Hello @Nagesh CL and welcome to Microsoft Q&A.
Private Endpoints are included in the ARM template. From your questions, it sounds like you want to have Private Endpoints in your development environment, but not in your production environment. I can tell you how to parameterize the Private Endpoints, but I haven't removed them from the ARM template before. I don't think the ARM parameter configuration can be used to discard items, so you would have to set up something to edit the ARM template after export.
Excerpt from continuous-integration-delivery: best practices:
Managed private endpoint deployment. If a private endpoint already exists in a factory and you try to deploy an ARM template that contains a private endpoint with the same name but with modified properties, the deployment will fail. In other words, you can successfully deploy a private endpoint as long as it has the same properties as the one that already exists in the factory. If any property is different between environments, you can override it by parameterizing that property and providing the respective value during deployment.
How to choose what gets parameterized in CI/CD
The Managed Identity is based upon the identity of the Factory itself. That is, when you select Managed Identity, Azure asks "has this Factory been assigned permissions on resource ____?"
If you want to change which resource the linked service points to, the specifics depends upon the resource type. All linked service parameterization properties can be found under "Microsoft.DataFactory/factories/linkedServices"
... "typeProperties"