Normally I blog about Microsoft 365, but today I want to give you a glimpse into one of my behind-the-scenes tools. As a video creator (see my online course and YouTube channel), I use Camtasia 2021 for all of my video editing and creation needs.
Often, I need to split video segments to remove pauses, create space, correct mistakes, etc. Below are the steps to accomplish that:
Select the media you’d like to split.
Move the playhead to the exact moment in the timeline you’d like the selected media split into two segments.
Select the split icon (a bisected rectangle).
After that, you may wish to move the two segments independently, delete or ripple delete one of them, edit segments independently, make additional cuts/slices, etc.
Comment if you’d like to see more tutorials on a specific action or process in Camtasia – I’m happy to help my fellow video creators get started.
You can open files directly within Teams to have a single context in which you’re able to do your work. However, when dealing with complex files you may wish to change how files are opened to be able to utilize the full functionality of the desktop app instead.
Note: You must use the desktop version of Teams to enable this feature (doesn’t apply to web version). If you’re still not seeing it, make sure you have updated to the latest version of Teams.
If you don’t make any changes to your default settings in Teams, documents will open in Teams automatically. Here are the three Teams file experience options you have:
Teams (default) – uses the Office web app, just like browser, but with Teams as a wrapper (see following screenshot)
App (desktop or client application) – opens outside of Teams and browsers in the fully-featured application (Word, Excel, or PowerPoint)
Browser – opens outside of Teams in the Office web app but in your internet browser
And, of course, you can always open a file in Teams then choose Open in Desktop App at the top, but that’s the long way around. We can choose where to open a file before we even open it.
In this post, I’ll cover how to open a file in a different context (Teams, desktop app, or browser) for one-time needs as well as changing your default setting to force all files to open in the desktop version if you wish.
How to open a file from Teams in the desktop/client app without changing default settings
If you right-click a file in Teams and hover over Open, you’ll see you can choose to open that one file using the default or your preferred experience (Teams, app/desktop, or browser). This is great for those one-off files that require the full desktop application.
So if you need to open a Word, Excel, or PowerPoint file outside Teams, using its full desktop app:
Right-click the file
Select Open in app
Or if you already have the file opened in Teams, just click Open in Desktop App at the top.
How to change default file opening behavior of Teams to always open in desktop app
If you’d rather change the default setting for yourself so that a single left-click opens in the desktop app always, there are two places you can change your file opening preference – a file’s open menu or your Teams settings.
Note: Desktop/app will only be available as an option if you have Office version 16 or newer.
Always open Teams files in the desktop app | Method #1 (from a file)
To change your default file opening preference from an individual file’s menu, right-click the file, select Open, then select Change default.
Then choose Desktop app and Save. Now Teams will always open Word, PowerPoint, and Excel files in the appropriate desktop application.
Always open Teams files in the desktop app | Method #2 (in your Settings)
Alternatively, you don’t need to find a file first. Simply use the ellipsis (three dots) in the upper right corner of Teams and choose Settings.
Then select Files from the left and choose Desktop app from the dropdown menu. You change is saved automatically.
Always open Teams files in the Desktop app | Bonus method (prompt after opening one-time in desktop)
There is one more way to change this setting, but it’s less straightforward so I’m deeming it a “bonus method.” 🙂
If you do choose to right-click > Open > Open in app one time for a file, when you return to Teams it will prompt you to let it know if you were just opening in the desktop app this one time, or if you would like to go ahead and change your setting to always open Teams files in the desktop app.
If you’ve just copied your multi-page Power BI report’s URL and pasted into the properties of a Power BI web part on a SharePoint page, you may have noticed your pages aren’t appearing as options in the Page name dropdown.
This is because the URL you copied from Power BI likely contained a specific page in the URL itself, ending in something like …/ReportSection1 (which is referring to a specific page already).
To fix this and have your pages show up as options in the dropdown, simply remove the ReportSection1 (or 2, 3, etc.) from the end of the URL in the Power BI report link box and try again.
To speed things along, I usually cut (Ctrl+X) the corrected URL, click outside the box to “reset” the web part, then paste (Ctrl+V) the corrected URL and wait for my page names to appear. This is demonstrated below.
Here’s a related video demonstrating how to embed a Power BI report on a SharePoint page including fixing the multi-page issue mentioned above.
If you’re trying to build business process flows, use Process Advisor, or use AI Builder in Power Automate, you’re going to need a database established in the intended environment first. If you don’t have a database in the environment yet, you’ll get an error as seen below:
Business process flow requires a Microsoft Dataverse database. Try a different environment or create a new one to start using business process flow.
You need a database to use process advisor. Create a database, or switch to an environment that has one.
AI Builder requires a Dataverse database. Create your database to start using AI models.
In the following sections, I’ll detail how to:
Switch to a different environment
Add a database to your current (or any) environment
Create a new environment with a database
Switch to a different environment
Your organization could already have multiple environments. Always check with your admins before making any uncertain decisions because environments could be used for specific data types, processes, geography compliance restrictions, etc. You may or may not have access to all of your organization’s environments depending on your specific organization’s governance and configuration.
Let’s assume you do have multiple environments and you’ve discussed with your admin or governance team which environments are appropriate for your specific need or project. To switch to a different environment that might have a usable database, click on the name of your current environment in Power Automate in the upper right, then choose the other environment from the side panel.
Add a database to your environment
You may choose to just stay in your current environment and add a database to it. If that’s the case, go ahead and click on Create a database and follow the right side panel’s wizard to complete the process.
Let’s assume your organization hasn’t yet created any additional environments you could use other than the default one that came with your tenant (which obviously doesn’t have a database or you wouldn’t be here 😄). If you don’t want to create the database in the default environment, you may wish to create a new environment with a new database.
Change the environment type from Production to Trial. This will allow you to proceed with provisioning the environment for your trial purposes. You can later convert this to Production, but only if you have more database capacity when you’re ready to do so.
Just trying to clean up a bit? Start your evaluation by going to the Power Platform admin center’s Capacity page to see what’s using up the most space. Are there things you could clean up? Notice any unusual usage?
Depending on what you find in the Capacity page, you may find yourself wanting to look more closely at environments. To do this, select the Environments node from the left-hand nav.
From Environments, you can select an environment and choose to view its resources which will give you a good idea of what might be using more than anticipated. Perhaps a flow or app just needs adjusted. You could, for example, open a listed environment and choose Resources > Flows, examine the flows using the environment, see their owners, and even disable the flows until further action can be taken to address the underlying issue.
Delete an environment
See any environments that could be deleted? Just keep in mind a deleted environment takes its resources and backups too – so consider any flows, apps, etc. that might need updated to use a different environment first.
If you do determine there are unused and unneeded environments in your organization, you can delete them from the Power Platform admin center.
If you’re attempting to use Solutions, AI Builder, certain Power Apps templates, etc. you may run into a situation where you’re working in an environment without a Dataverse (formerly known as Common Data Service) database. This will prompt you to create a new environment or database as a power user (if allowed).
Create a new environment with a Power Apps per user plan
Once you’ve been licensed with a Power Apps per user plan, you’ll be able to create a solution and use existing or create new environments unless your admins have limited who can create new environments.
If you’re allowed, you can simply begin building your flow or app as you normally would, but now that you’re licensed appropriately, you’ll be able to choose to create a new environment in-context as you go. For example, let’s say there are no environments with databases you can use for a new Assets Checkout app you want to build from a template in Power Apps. Simply begin building the app from template, and choose to Create new environment when prompted.
Then in the panel that appears to the right, give the environment a name, choose a data region, and environment type. Then choose Create environment.
Verify your currency and language. And if you’re creating a sample app (as we are in this scenario) you’ll also decide whether to bring in the sample data with that template. When satisfied, click Create my database.
Now as you’re building solutions in the Power Platform, you can switch between environments by selecting the name of the active environment and choosing the environment in which you wish to build (or utilize data from).
Now let’s create an environment from the Power Platform admin center as an admin.
Create a new environment as an admin in the Power Platform admin center
This is arguably the better method to use at an organization level to make sure your environments have a consistent naming convention, no efforts are duplicated, and boundaries are clear from one environment to another. With each environment potentially belonging to a different geography depending on how it was set up, this could be a significant compliance concern for some sectors. If you need to restrict environment creation to admins only, check out this other post. Otherwise, let’s proceed with creating a new environment for your users from the Power Platform admin center.
Name and describe your new environment, and choose the region in which its data needs to be stored. You’ll also choose type (Trial, Sandbox, Production, etc.). If this environment is going to be used to store and use data, you’ll want to also enable database creation (creates a Dataverse database). Click Next when ready.
Then choose the language, currency, and additional options (including restricting usage to a specific security group). Click Save when ready.
You (and/or your organization’s users whom are allowed to use the environment) will now be able to connect to the environment and any of the tables within its Dataverse database. This Dataverse connection can be used in Dynamics 365 apps, Power Apps portals and apps, and Power Automate flows.
Note: This post applies to traditional environments, not Dataverse for Teams environments. Thanks to Loryan Strant for adding that clarification.
As long as someone in your organization is on a Power Apps or Power Automate per-user plan, they may have permission to create their own environment (unless you’ve already limited it previously in your organization). These environments can be used and shared by Dynamics 365, Power Apps portals and apps, and Power Automate flows. Environments can house multiple Dataverse tables (which can also be provisioned by a power user with appropriate licensing). Power Platform apps and Dynamics 365 can then connect to, read from, and write to these tables which would likely be shared across multiple applications/processes.
For example, if Megan Bowen is licensed on a Power Apps per-user plan she would, by default, be able to create new environments as she wished. And with the right training and deployed best practices, this may not be an issue. But if training isn’t provided and users are creating environments left and right, it may be time to limit who can create them (regardless of their licensing) until proper training and governance can be deployed.
So if you wish to manage environments centrally and prevent environment sprawl, you will want to limit the ability of users in your organization so they can’t create their own environments. Doing this may slow their individual productivity, but could also prevent duplicated efforts, inconsistent data organizationally, scattered naming conventions, and more. As long as you replace this restriction with a formal and effective governance policy, request form, etc. it will minimize disruption to your colleagues’ productivity.
Ready to do this? Let’s go over the steps to limit Microsoft Power Platform environment creation and management.
Limit new environment creation via the Power Platform admin center
Note that this doesn’t remove existing environments or limit the abilities of their creator(s) to continue managing pre-existing environments. This setting will only apply to new environments and prevent additional unwanted sprawl.