Deploy Like a Pro: Power Platform Pipelines Tutorial (Step-by-Step)

Поделиться
HTML-код
  • Опубликовано: 6 фев 2025
  • Tired of manual deployments in Power Platform? Say hello to Pipelines, your new best friend for automated and streamlined solution rollouts! In this comprehensive step-by-step tutorial, we'll guide you through everything you need to know, from setting up your environment to deploying your first solution. Whether you're a beginner maker or a seasoned developer, this video will equip you with the skills to confidently manage your Power Platform applications.

Комментарии • 43

  • @MbueloRamafamba
    @MbueloRamafamba 11 месяцев назад +3

    You came through for me

    • @Tiyani365
      @Tiyani365  11 месяцев назад +1

      😉 Glad you like it

    • @MbueloRamafamba
      @MbueloRamafamba 11 месяцев назад +1

      @@Tiyani365 right on point. we should chat sometimes about D365 over coffee. There's actually 2 ways to do pipelines. This way and also the devops way, which can allow you to also point to specific code in cases where you might have externally running code

  • @justcathy6729
    @justcathy6729 11 месяцев назад +1

    I'm no DevOps person but this is something I need, deployment night will never be the same, thanks Tiyani. indeed #1000subs

  • @alphabetty6171
    @alphabetty6171 Месяц назад +1

    Great video

  • @Bamwich
    @Bamwich 3 месяца назад +1

    could you cover delegated deployments and more importantly the approval process that is required with them?

    • @Tiyani365
      @Tiyani365  28 дней назад

      Hi @Bamwich, thanks for the support. it is in the pipeline :)

  • @MrAnonymous3333
    @MrAnonymous3333 3 месяца назад +1

    What licence is required to create Power Platform pipelines

    • @Tiyani365
      @Tiyani365  28 дней назад

      Hi @MrAnonymous3333, if you have a developer license you are sorted as this is part of the power platform

  • @Slash1066
    @Slash1066 8 месяцев назад +1

    Great video, learned some good tips

    • @Tiyani365
      @Tiyani365  8 месяцев назад

      Great to hear you’re getting value

  • @prashantdhage1345
    @prashantdhage1345 4 месяца назад +1

    why solutions are deployed as managed?

    • @Tiyani365
      @Tiyani365  28 дней назад

      @prashantdhage1345 this feature works with managed solutions, doesnt yet have flexibility to chose whether you want unmanaged or managed. for full control I recommend using Azure DevOps or GitHub Actions

  • @owenwetherow
    @owenwetherow 7 месяцев назад +1

    Great video Tiyani

    • @Tiyani365
      @Tiyani365  7 месяцев назад

      Thanks @owenwetherow glad you like it

  • @mogahidsabeel4988
    @mogahidsabeel4988 2 месяца назад +1

    Hi there, thanks for the video.
    I deployed a solution (managed) in production environment using Pipeline. If I need to make changes to the flows/app afterwards, i.e. to o update the solution, how to go about that?

    • @Tiyani365
      @Tiyani365  Месяц назад

      For this deployment process it’s managed solutions. You can use the service account to run your deployment as this simplifies things and consider using environment variables in other cases where values a different for your flows

  • @josephlim2064
    @josephlim2064 8 месяцев назад +1

    How about deployment settings - environment variables and connections? Where do we specify these?

    • @Tiyani365
      @Tiyani365  8 месяцев назад +1

      you can definitely create the JSON deployment settings file using pac command and link it to one of the steps in your pipeline, for each environment. on the step there's a checkbox when checked it allows you specify the deployment settings file. I have a detailed video coming soon regarding this so stay tuned.

  • @JavidBahramzy
    @JavidBahramzy 8 месяцев назад +1

    How would you handle custom C# and JavaScript code? For example Plugins and form scripts?

    • @Tiyani365
      @Tiyani365  7 месяцев назад

      Hey @JavidBahramzy, if you use C# plugins, plugin steps, JavaScript, or even custom web resources, all of these components will be deployed to the target Power Platform environment as part of the process.

    • @JavidBahramzy
      @JavidBahramzy 7 месяцев назад

      @@Tiyani365 yes but regarding the build and release pipeline, how would you handle these custom code components like plugins and JavaScript? I mean the assembly containing plugins and all its dependencies must be built, packaged and added to the solution. Does the DevOps build tools for power platform have tasks to support that. The examples I have seen about power platform build tools only show exporting and importing solutions containing standard components. Are custom components like Plugins, Custom workflow activities and JavaScript also supported? Are there any examples and best practices?

    • @Tiyani365
      @Tiyani365  7 месяцев назад

      Hi @JavidBahramzy, This process is a bit different from Azure DevOps. It's designed to streamline deployments between environments, but the configuration options are still ramping up (Microsoft's definitely working on expanding them though!).
      If you need more control and customization, I'd recommend checking out Azure DevOps. It lets you run scripts to build your code and even use deployment settings files for those specific tweaks.

  • @josephlim2064
    @josephlim2064 8 месяцев назад +1

    Great stuff! From the video, it seems the PP Pipelines does not support multi-geo environment/region. What do you suggest for such scenario? Thanks

    • @Tiyani365
      @Tiyani365  8 месяцев назад +1

      you are correct power platform pipelines don't currently support multi-geo regions. I would suggest to use azure DevOps/GitHub action as you have much control of each stage. I will check with the team and give more feedback regarding this.

  • @LauraLuisaRosenberg
    @LauraLuisaRosenberg 5 месяцев назад +1

    I noticed a new security role called "Deployment Pipeline Default" when I was trying to add roles. I haven’t seen any mention of this in the documentation. Does anyone know more about it or could provide some guidance?

    • @Tiyani365
      @Tiyani365  28 дней назад

      Hi , this role is used for managing your code and artifact, it allows for a base permissions when performing tasks specifically when running pipelines so as not to give too much privileges. hopwe this helps. :)

  • @josephlim2064
    @josephlim2064 8 месяцев назад +1

    Is it possible to select deploy unmanaged solution, instead of the managed one?

    • @Tiyani365
      @Tiyani365  8 месяцев назад +1

      100% you can deploy unmanaged solutions but keep in mind that best practice for production deployments is managed as this makes it easy to roll-back if something goes wrong

  • @aravindreddyakiti480
    @aravindreddyakiti480 11 месяцев назад +1

    Each time we need to create a new solution?

    • @Tiyani365
      @Tiyani365  11 месяцев назад +1

      When using managed solutions it’s not a must but you can still create a new one every time depending on the requirements

    • @aravindreddyakiti480
      @aravindreddyakiti480 11 месяцев назад

      @@Tiyani365 hi, is there any way to set the power automate flow owner from this deployments

    • @Tiyani365
      @Tiyani365  9 месяцев назад

      @@aravindreddyakiti480 you can by changing the owner of the flow to service principal application before deployment

  • @lufunot5297
    @lufunot5297 11 месяцев назад +1

    This I have been waiting for, ♥♥ #1000subs

  • @Xitlavangoma-fo4sp
    @Xitlavangoma-fo4sp 11 месяцев назад +1

    Swikahle leswi, hakhensa Tiyani

    • @Tiyani365
      @Tiyani365  11 месяцев назад

      Kukhensa mina

  • @QueenMagomani
    @QueenMagomani 11 месяцев назад +1

    Another one, Road to #1000subs

  • @stevebunn5995
    @stevebunn5995 11 месяцев назад +1

    Keep up the good work, #1000subs

    • @Tiyani365
      @Tiyani365  11 месяцев назад

      Thanks! Will do!

  • @t-boss5903
    @t-boss5903 11 месяцев назад +1

    #1000subs