Connect with me: ☕Buy me a coffee: www.buymeacoffee.com/danchristian 🖇LinkedIn: www.linkedin.com/in/danchristian19/ 🚀 Instagram: instagram.com/dan.christian.33/ X (Twitter): twitter.com/dchristian19
Environment routing is good some how the developer environment marked as managed as it produce additional cost when we use any connector consider as premium which is not helpful in terms of coat hopefully this option should allowed non managed environments in near future thanks for your explaining ❤
Hi Daniel, thank you for the useful content. I wanted to ask your help which may be slightly off-topic. Can you please share what Power Platform Architect does in details and how to prepare for this kind of role? Thank you in advance.
Thx for Sharing, Very Well Explain as Always. I got 5 Questions ; 1) If the user connect to power automate, is this routing working also? 2) When the devevelopper got redirect to his new environment, what about his old content in the default invironment, does the move automacticaly or the developer should get back to default environment to work on his old app ? Does the developer got automacticly the License comunity assign since Managed Environment require license? 3) there was a rule by Microsoft developer enviroment get deleted after 4 months without usage, is this rule still apply? 4)Last year Microsoft Allowed Developper to Create 3 Developer Type Environment, Allowing this feature as and admin, won't we be Submerged by a float of dev environment? 5) Regarding license Strategy, is this a good Practice to apply on company that is not so mature on the power platform, since Managed enviroment require license for all user accessing it ? Thanks in advance for you reply !
