Hi @Rajendar Talatam (US - IFS) ,
You could use runbook parameters and have a single runbook with your environment name as a parameter. In the stage where you get the environment name for which your runbook has to run, in that level itself you could remotely create schedule with the help of New-AzAutomationSchedule Az PowerShell cmdlet and then remotely configure the schedule of the runbook specific to particular environment with the help of Register-AzAutomationScheduledRunbook Az PowerShell cmdlet's parameter section. For reference, please check below screenshot.
If you have further queries on how to automatically get the environment name for which your runbook has to run and configure the schedule, then please provide end-to-end context of your use case i.e., where and how do you define that runbook has to run for a particular environment at a given point of time, what are the services, tools or technologies involved, etc.