Save list as template on modern team site
Wonder if anyone can advise how I can create a list in a modern sharepoint team site from a template that I saved from a classic team site. I don't see any option from within powershell settings. I have been getting my head around all the various sharepoint resources and have been creating lists etc on my classic team site for now but our users are starting to use the modern team sites created from Office 365 groups and I really would like to have them use some of the list templates I've created. Any help appreciated.SharePoint Online Backup Strategies for a Cloudy Day
With an ever-growing Office 365 ecosystem, the question of data backup and recovery often arises. The data used in the apps is stored across multiple SharePoint Online sites, Exchange Online mailboxes, and other specific apps. There are two types of backup scenarios that may you need to cope with Service backup, which ensures that all the content is backed up on a regular basis in the case there is corruption or the service fails Deletion backup, where users will accidentally or purposely delete content In SharePoint Online, by default, content is stored indefinitely in your sites. Without someone explicitly deleting the content or having information management policies or other external actors that would delete content, you don't have to worry about your data disappearing. But, in reality, there will be scenarios, where content is purposely or inadvertently deleted. Whether it's a single file or entire site collection, you need ways to get your data back. Before we look at the types of solutions available, ask yourself what it is you really need to back up and why. Wiping out your intranet will likely cause disruption to your organization, but will you be able to recover from it? You can break down your SharePoint environment into several layers Documents - Word, Excel, PDF, or whatever format you work in. This is the key work product your teams depend on and one of the core reasons SharePoint, an Enterprise Management System) is being used. Documents are created and updated frequently across the sites List Items - Calendars, action items, risks registers, etc. Like the Documents, these are core to your SharePoint environment and change frequently. Metadata - Over the years, there has been a lot said about the importance of metadata. There are many great reasons for having it. Yet, without discounting any of the reasons, as long as the core metadata can be recreated from the content itself, you're probably safe. Some metadata will be manually set by users once a document is created or is modified (for example, changing a status). Other metadata, such as Modified by or Modified date will change automatically. Site structure - The site structure entails everything else that makes up your SharePoint site - information architecture, navigation, branding, custom web parts, and other elements that make the SharePoint the IT centerpiece of many organizations. Lots of effort is spent in setting it up, and once you've reached that point, the rate of change to the environment itself is lower than content itself. Now, imagine that your SharePoint environment got destroyed (picture a virtual meteor). What would it take to get your organization back up and running in the shortest time possible? Remember how you used to work before SharePoint. Like a good science fiction movie, where all metropolitan cities are destroyed and people are living out of run-down campers, you may find yourself going back to the days where documents were stored on network drives and lists were Excel worksheets (but only for a short while). Today, third party software providers offer some great options for backing up your cloud content. However, these solutions are often costly and may be too advanced for your specific use case. Let's have a look at some alternative options you have. Document Version Control This is the simplest solution available to you. As a document gets updated, new versions are created. At any time you can get back to an older version and even restore it as the current version. When using versions, you can control how many versions will be saved at any time. For instance, suppose you set the limit to 50 versions. Once you have reached 50 versions for a document and save it again, version 1 will be deleted and you will be left with versions 2 to 51. Keep in mind that for each version stored, you are storing a copy of the document, hence taking up additional space on your tenant. Using the SharePoint Recycle Bins When documents or list items are deleted, they go to the User recycle bin (first-stage recycle bin). Content remains there for 93 days, during which the user can restore the content to its original location or delete it from the User recycle bin. Content deleted from the User recycle bin moves to the Site Collection recycle bin (second-stage Recycle bin) for the remainder of the 93 days. The second-stage recycle bin can contain anything from a single item to entire site collections. To restore content from the Site Collection recycle bin, you will need to contact your site collection administrator to restore the data via the SharePoint Online Administration Center Recycle Bin (https://<tenant>-admin.sharepoint.com/_layouts/15/online/RecycleBin.aspx) Requesting Backups from Microsoft If content was deleted permanently from your SharePoint Online environment, you may still be able to get it back for a limited amount of time directly from Microsoft. In this case, a user with Office 365 global admin rights will need to contact Microsoft through the help channels to request a restore. The restore process will bring back an entire site collection with all its content to the original location. This is important to remember as you may have only lost a single file and will need to manually reconcile all the other content. Microsoft backs up content every 12 hours, and take a few days to restore, so depending on the urgency for getting the data, this may not be a viable solution. Retention Policies The purpose of Retention Policies is not to act as a backup for your data, but rather restrict what data can be deleted (or should be deleted) and when. The decisions to keep to delete content are usually bound by regulatory or legal policies. With Retention Policies you can apply such rules to all content or just content meeting certain conditions, such as content containing specific keywords or specific types of sensitive information. When content is subject to a retention policy, you can continue to modify your content in its original location. But if someone edits or deletes content that’s subject to the policy, a copy is saved to a secure location where it’s retained while the policy is in effect. To further restrict how your content is handled, Retention Policies can be configured so that once they have been turned on for a specific piece of content, they cannot be turned off or made less restrictive. To meet this requirement, you can use Preservation Lock. After a policy’s been locked, no one—including the administrator—can turn off the policy or make it less restrictive. Again, the Retention Policies are a safeguard against accidental (or malicious) deletion of content, not backup. If you introduce a Retention Policy that permanently deletes content, you will not be able to get it back once the policy takes effect. Manual Content Backup Alerts Alerts themselves are not a backup method. However, you can use them to stay informed if there is any sensitive information being deleted and allows you time to determine how to react. For instance, if there are specific document libraries you mostly care about, you can enable alerts on them for document deletion, which will then give you time to decide what to do once the documents are in either the first-stage or second-stage recycle bins Use a Flow to act on modified or deleted content Microsoft Flow offers a number of triggers and actions that can help you automatically react to events where documents or items are deleted or modified. The Flow would use an item/file deleted or item/file modified as a trigger to start the workflow. Based on your specific scenario, you could then decide what you want to do with it. For example, copy the file to another location, such as SharePoint site, Azure storage, OneDrive for Business, file system, or other service or simply send an email with the file's information (similar to an alert). To maintain the existing metadata, you can export it together with the file in the form of an XML structure or similar. This way, you could recreate it in the case you need to restore the file. Depending on the size of your organization and amount of content being created or modified, you need to consider the number of such workflows that would be triggered so that you are within the limits of your service plan. By default, a user can run up to 2,000 workflow executions in a month. PowerShell to copy data PowerShell will give you lots more flexibility, but comes at a cost of developing and maintaining the scripts. Using PowerShell, you can write scripts to automate much of these backup activities to copy files, extract metadata, and manage the content and report on it from another location. OneDrive for Business Syncing With OneDrive for Business, you're able to sync specific document libraries to your local machine. The same scenario could be set up using a service account that will sync content from SharePoint Online to a folder on a network file share. This continuous mechanism is easy to set up, but you need to ensure two things - 1) you are still responsible to back up your file share and 2) you need to also set up a mechanism that will copy the content from the sync folder to another location on your file share or other location outside of your SharePoint or OneDrive for Business setup as files deleted from the document library will also be removed from the sync folder, which is what you're trying to avoid with this backup setup. Leveraging Migration tools If you have already made an investment into a migration tool, you may be able to leverage it for your backup needs. Most migration tools allow you to do delta migrations, where only content that have changed is migrated. Furthermore, such migrations can often be scheduled to run at specific times. This lets you run the migrations when system usage is low to minimize the impact on your organization. If you are using a migration tool that offers these features, then you should set up a one-way migration/sync that will pull data from your active SharePoint environment and copy it to a backup location. Depending on your needs, you can migrate specific document libraries or entire site collections to a number of locations - another site collection in your existing tenant, a separate tenant, Azure, an on-premises SharePoint farm or file share, or more. Obviously, there are cost and infrastructure implications to each. For example, storing the content in an on-premises SharePoint farm will require you to maintain a separate farm and infrastructure to support it. If you are copying the content to another location within your tenant, your backup may be compromised if your tenant or the data center it's managed from becomes unavailable. Having an alternate tenant in a different datacenter provides a level of redundancy, but at an additional cost. You can, however, reduce the cost by adding your users to the alternate site collection but not license them. This way, the ownership of content can remain the same, but license costs are not incurred. Just remember that in order to achieve this, you will also need to sync your user accounts (minus the licensing part). Regardless of which way you go with a migration tool, one of the largest advantages you have over the Microsoft Backup request is that you can restore granular content as needed or even an entire site collection to another URL so you can pick what to keep. As you can see, there are a number of viable options available for backing up your data in SharePoint Online that don't require you to invest in an expensive solution. As with anything else in Office 365, proper governance is important to reduce the risk of inadvertently deleting content you may need and having a way to get it back if accidentally deleted.
UPDATE: Create Office 365 Groups with team sites from SharePoint home moving beyond First Release
We recently completed the worldwide rollout for Office 365 Groups getting full-powered SharePoint team sites at the end of January 2017. Our next step is to now bring the ability to create SharePoint team sites connected to Office 365 Groups from SharePoint home beyond First Release. This next phase of rollout will begin today, and is expected to reach all customers worldwide over the next month. We also wanted to share some of the additional capabilities we’ve added to group-connected team sites since we first began roll out to First Release. No matter where you create an Office 365 Group from – whether SharePoint, Outlook, Microsoft Teams, Yammer, or elsewhere – you consistently get the full collaborative power of a connected SharePoint Online team site among the other services groups provides (shared inbox, shared calendar, Planner plan, team notebook, and more). This move beyond First Release includes the capabilities described in our November blog post: Fast creation of sites connected to Office 365 Groups from the SharePoint home page Editable team site home pages that look great at your desk and on your phone Modern creation panels for new libraries and lists In-place navigation editing Site settings panels for editing site information and site permissions Modern page creation in classic sites Admin controls for team site creation The site permissions panel listed above has been enhanced to include options for adding members to the site’s Office 365 Group or simply sharing only the team site without providing access to other group resources. The panel is intended to provide simple permissions management, but also includes a link to ‘Advanced permission settings’ for site owners that have a need to do things like add custom SharePoint permissions & mappings. Note this panel also allows you to add users or groups to the ‘Site Visitors’ permissions group, so it is easy to provide read-only access to the site. All you need to do is add a new person or group via the ‘Invite people’ button, and then change their permission level to ‘Read’. The user or group’s permission level determines which permission group they appear under – those with ‘Read’ permission will appear in the ‘Site Visitors’ category. Managing group-connected team sites Since new team sites are connected to Office 365 Groups, managing them involves possible interactions with Office 365 Group settings in addition to those provided by SharePoint. Examples include settings that apply to groups such as whether group creation is allowed in the tenant, which users are permitted to create groups, usage guidelines URL or group classification labels. Once the group-connected site is created, management of the site is likewise split between Azure Active Directory (AAD) PowerShell cmdlets and the SharePoint Online Management Shell. Anything dealing with creation, deletion, un-delete (restore) or membership happens through AAD. SharePoint-specific management, such as storage quota and link sharing policies, take place using the SharePoint management tools. For governing modern site creation, this support page details the administrative controls, but is useful to summarize the relationship between a group’s policy settings and how the SharePoint ‘Create site’ experience behaves. By default, if group creation is enabled in the tenant, the ‘Create site’ command will appear on SharePoint home, and if a user is permitted to create groups they will get the site creation experience. If the user is *not* permitted to create groups, they will get the classic self service provisioning experience that results in the creation of a subsite. The table below describes how the combination of group and site creation settings work together: * The current user is considered to have group creation permissions if the AAD property EnableGroupCreation is true, or it is false but the user is a member of the security group assigned to the GroupCreationAllowedId AAD property. ** Site creation is enabled via SharePoint Admin Center under Site creation settings: In addition to managing site creation, we are also enabling the SharePoint Online PowerShell cmdlets to administer modern, group-connected site collections. This means that modern team site collections can now be enumerated with the Get-SPOSite cmdlet with the following example: Get-SPOSite -Template GROUP#0 -IncludePersonalSite:$false Most parameters for these site collections can also be set using the Set-SPOSite cmdlet, with the exception of those that would result in breaking connection with their corresponding Office 365 Group (e.g. you cannot set the Owner property using this cmdlet – you would need to set the Group’s owners via AAD). Please refer to the respective documentation for each of the above cmdlets for additional details. For more information on using PowerShell to manage Office 365 Groups, this article may be helpful as well. What else is new? In addition to the above, this phase of the rollout includes a couple of previously unannounced capabilities. The first is a group membership management experience that lives in SharePoint itself. Now, when you click on the member count of the group in the site header, you will be presented with a new group membership panel that allows you to add members and change their roles between owners and members, or remove them outright. Users will no longer need to jump to Outlook to manage the group’s membership. The second is Content Type Hub syndication – modern sites can now consume content types that have been published from a central content type hub. We heard feedback that this is an important feature to enable, and we are including it in this rollout. As noted above, this rollout will take place over the course of a few weeks. We are very excited for you to take advantage of modern, connected team sites and look forward to any feedback or questions you may have. As always, please ask in a reply to this thread. Thanks, TejasList all Site Collection Admins Powershell
Hello, I am trying to get all site collection admin for the sites in the tenant using Powershell. However, the cmdlet Get-SPOSite fetches only the primary site collection admins. The only way to get all is if I grant my admin account access to the site collections. Since the site collection admins can be viewed from the admin console, there should be a way to get them. Is there any cmdlet or api that I can add to my script? Thank you. Bhavpreet BainsSharePoint - How to Reset Inheritance Permission set into an SP DocLib folder or file
When we are importing File Server content into SharePoint using dedicated tools for, we can import permission set configured at the sub levels (subfolders or documents). That import can create some issues due to incorrect configuration in place on original File Server. But how can we check one user complaining to not see or access the content as it was into the File Server ? That need to be reviewed at any SharePoint Content Level with Permission Management with "Administrator Permission" with the link "Manage Access". You have to select the link (at the bottom) "Advanced" to have the exact permission set configured at this level Based on that situation, you can decide what to apply at this folder or file level. You can: add a colleague or a group with appropriate permission (Read, Write or full control) Remove the specific permission of that level clicking on "Delete unique permissions" But this config could concern many other sublevels and wait the user complains is probably not the best option. How to track folders or files with unique permissions ? You can do that using the Document Library Permission Settings from: Library Settings > "Permissions for this Document Library" You will have the permission configuration in place at this root Document library level. But the first line will explain (if that is the case into your document library) the status of sublevel: Some items of this list may have unique permissions which are not controlled from this page. Show these items. When you are clicking on that link it will show you a part of customized levels. You can change the permission set for each of those level clicking on "Manage Permissions" to have the same details we look in the first part of this message. Now as you can imagine with a document library could contains thousands of folders, this manual action is really huge. How reset all customized permissions configured at sublevel ? That is the best option you can select as site admin, using PowerShell and an interesting PS Module named: SharePointPnPPowerShellOnline This following script will help IT Team to reconfigure all content customized into the document library and cancel this and reconfigure permission inheritance instead. #install-module SharePointPnPPowerShellOnline -Force #to install that module the first time only Write-Host " ---------------------------------------------- " Import-Module SharePointPnPPowerShellOnline Write-Host " ---------------------------------------------- " #Config Variables $SiteURL = "https://yourtenant.sharepoint.com/sites/YourSiteCollection/" $ListTitle = "Document Library Name" $foldertoscope = "/sites/YourSiteCollection/YourDocumentLibrary/" #Connect to PnP Online Connect-PnPOnline -Url $SiteURL -UseWebLogin $ctx = Get-PnPContext $ctx.Load($ctx.Web.Lists) $ctx.Load($ctx.Web) $ctx.Load($ctx.Web.Webs) $ctx.ExecuteQuery() $ll=$ctx.Web.Lists.GetByTitle($ListTitle) $ctx.Load($ll) $ctx.ExecuteQuery() ## View XML $qCommand = @" <View Scope="RecursiveAll"> <Query> <OrderBy><FieldRef Name='ID' Ascending='TRUE'/></OrderBy> </Query> <RowLimit Paged="TRUE">5000</RowLimit> </View> "@ ## Page Position $position = $null ## All Items $allItems = @() Do{ $camlQuery = New-Object Microsoft.SharePoint.Client.CamlQuery $camlQuery.ListItemCollectionPosition = $position $camlQuery.ViewXml = $qCommand ## Executing the query $currentCollection = $ll.GetItems($camlQuery) $ctx.Load($currentCollection) $ctx.ExecuteQuery() ## Getting the position of the previous page $position = $currentCollection.ListItemCollectionPosition # Adding current collection to the allItems collection $allItems += $currentCollection Write-Host "Collecting items. Current number of items: " $allItems.Count } while($position -ne $null) Write-Host "Total number of items: " $allItems.Count for($j=0;$j -lt $allItems.Count ;$j++) { if($allItems[$j]["FileRef"].StartsWith($foldertoscope)) { Write-Host "Resetting permissions for " $allItems[$j]["Title"] ".." $allItems[$j]["FileRef"] $allItems[$j].ResetRoleInheritance() $ctx.ExecuteQuery() } } Now you can adapt the permissions as much as you need to Fabrice Romelard
How to Properly Delete Custom Columns in SharePoint
SharePoint custom columns have been around for quite some time, but I’m finding that there’s still some confusion on how the various types are used, and more importantly how can you delete them. In this post, I’m hoping to shed some light on the topic. Custom columns form a part of your overall SharePoint Information Architecture. When properly set up, custom columns (or fields as sometimes referred to in SharePoint) are ideal for capturing metadata in a consistent way across various types of content. In SharePoint, you can create custom columns in one of two ways: Custom List Column Custom List columns are created directly within a list (or library). They can be accessed via the list and used to store information. Although quick to set up, one of the major drawbacks is that list columns are limited in scope to only the list in which you created them. You cannot leverage the site columns outside of the list. This reason alone can prevent such columns from being considered for scalable solutions where you would have to add the same columns to multiple lists or libraries throughout a SharePoint site. Custom Site Columns Custom Site columns, as their name suggests, are created at the site level. Unlike their List Column relatives, the Site columns are accessible throughout the entire site collection, where you can add them to any number of lists, libraries, and content types. When you change the Site column properties, you have the choice to propagate these changes to all instances where the Site column is in use. Deleting Custom Columns If you wish to remove a custom column, it’s important to understand your options and the ramification they have on your data as described below. Deleting a List Column As I’ve mentioned earlier, when you create a new column within a list or library (not selected from pre-existing site columns), the list owns the column, and the column is only accessible to the list. Therefore, you can easily delete it from the List Settings by selecting the column and then clicking the Delete button on the form. Keep in mind that once you delete the list column, you also lose any data associated with the column. Deleting a Site Column from a List A reference to the site column is added when you add a site column directly to a list. As mentioned above, whenever you change the site column, any instances that use it will change as well. In the example below, I’m showing a Date field that has been added directly to two lists. If you try and delete the Date site column, you will see a warning message similar to This site column will be removed and all list columns which were created from it will be permanently orphaned. Are you sure you want to delete this site column? What does orphaned mean? Well, think of the site column as being the parent that controls its children (the referencing site columns within the lists). They will behave as their parent does. When you delete the parent, then you are in essence converting the site columns within the lists into list columns that lose the relationship between them. In other words, each list will have its unique copy of the site column with all the same settings just before you deleted the site column. You cannot undo this change. Deleting a Site Column from a Content Type When you add a site column to a content type, you’re following better practices for your Information Architecture by encapsulating all required metadata into a reusable entity (content type) rather than dealing with the individual site columns in each list. On the flip side, deleting your site column now becomes a bit trickier. If you tried to remove a site column that is associated with a content type, you might have seen a message as Site columns which are included in content types cannot be deleted. Remove all references to this site column prior to deleting it. What you need to do in this case is remove the site column from each content type before removing it. But what do you do if you don’t know where it’s used? In this case, you can leverage PowerShell to help you get the answer you need. To find out what content types are using your site column, you first need to know the InternalName of your site column. You find it by going to the site column (Site Settings à Site Columns) and looking at the URL as depicted below. In my case, the field is called Date1. Now you can run the script below that is based on OfficeDev PnP to search all the content types in a site collection. The script lists all the content types that use the site column you wish to delete (NOTE: to run the code I’ve supplied below, you must install the OFficeDev PnP solution first from https://github.com/OfficeDev/PnP-PowerShell). Connect-Sponline -url "your_tenant_url" $fieldInternalName = "your_field" $web = Get-SPOWeb Write-Host "Searching for:" Write-Host "InternalName: $fieldInternalName" Write-Host Write-Host "Get Content Types" $cTypes = Get-SPOContentType | where {($_.Hidden -eq $False) -and ($_.Group -ne "_Hidden")} # Search through all the non-hidden content type and find which ones include the site column foreach($ct in $cTypes) { $fields = $ct.Fields $web.Context.Load($fields) $web.Context.ExecuteQuery() $field = ($fields | where {$_.InternalName -eq $fieldInternalName}) if ($field -ne $null) { Write-Host "Content Types: $($ct.Name)" Write-Host "Content Type ID: $($ct.ID)" } } The output will look something similar to the image below. Searching for: InternalName: Date1 Get Content Types Content Types: TestCT Content Type ID: 0x01010038A3F80D4105C845BDD6A523CB1CC969 Now you need to go to the Content Types (Site Settings à Site Content Types) and look for the content types by name. If you see any duplicates, compare the content type ID against the one listed in the URL. Just remember, removing the columns from the content type will delete the content of those columns. That’s it. Now you know what to look for when removing your custom columns. Good luck.
PowerShell Modules for SharePoint Online Administrators
As a SharePoint Online administrator, you have several tools available to you for automating tenant administration. When you are setting up a new workstation it can be challenging to figure out what to install and where to get it. This post summarizes the various PowerShell tools available for managing your SharePoint Online tenant and related components in Office 365. SharePoint Online Management Shell This is used for performing core SharePoint Online service administration. Option #1 Download and install the SharePoint Online Management Shell Download sharepointonlinemanagementshell_<version>_x<32/64>_en-us.msi Run the installer Once installed you can load this module into your scripts using: Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking Option #2 Install the SharePoint Online Management Shell from the PowerShell Gallery (Preferred) If your operating system is using PowerShell 5.0 or newer, you can install the SharePoint Online Management Shell by using the following command: Install-Module -Name Microsoft.Online.SharePoint.PowerShell More information: Announcing availability of SharePoint Online Management Shell from PowerShell Gallery Getting started with SharePoint Online Management Shell What is the SharePoint Online Management Shell? Office Dev PnP PowerShell Module This solution contains a library of PowerShell commands that allows you to perform complex provisioning and artifact management actions towards SharePoint. The commands use CSOM and many can work against both SharePoint Online and SharePoint Server. Installing the module from the PowerShell gallery: Install-Module SharePointPnPPowerShellOnline -AllowClobber More information: PnP PowerShell overview SharePoint Online Client Side Object Model (CSOM) For scenarios that are not covered by the SharePoint Online Management Shell or the Office Dev PnP PowerShell module you may be able to accomplish what you need with access to the client side object model. Installing Package without Visual Studio installed 1. Download the NuGet Commandline: 2. From the directory where you saved nuget.exe run Nuget install Microsoft.SharePointOnline.CSOM -OutputDirectory C:\<TargetDIR>\SPO_CSOM More information: Microsoft.SharePointOnline.CSOM Package Information Azure Azure AD Management Shell This is used for managing top tenant level settings and for managing user provisioning and licensing. This requires global administrator rights and will not be necessary for many SharePoint operations. Installing Azure AD Management Shell V2: Install-Module -Name AzureAD More information: Azure Active Directory PowerShell for Graph Azure Azure AD Management Shell (V2) on PowerShell Gallery Security and Compliance Center In your role as a SharePoint Online Administrator you may also be asked to manage some or all of the Security and Compliance center in Office 365. Managing this with PowerShell requires the use of Windows PowerShell Remoting. Assuming the prerequisites are configured, you can connect to the Security and Compliance Center as follows: #Enter credentials and establish connection $UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://ps.compliance.protection.outlook.com/powershell-liveid/" -Credential $UserCredential -Authentication Basic -AllowRedirection #Import cmdlets Import-PSSession $Session #Once you are done with your session be sure you disconnect Remove-PSSession $Session Note: If your account requires multifactor Authentication you must also have the Exchange Online Remote PowerShell Module, please see Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication for more details. More information: Connect to the Office 365 Security & Compliance Center using remote PowerShell PowerApps With the preview launch of the PowerShell cmdlets for app creators and administrators, you can automate many of the monitoring and management tasks that are only possible manually today in Power Apps or the Power Apps Admin center. Install the administration module: Install-Module -Name Microsoft.PowerApps.Administration.PowerShell Install the creator module: Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber Once installed you connect to PowerApps as follows: #Commercial Add-PowerAppsAccount -Endpoint "prod" #GCC - Not GCC HIGH or DOD Add-PowerAppsAccount -Endpoint "usgov" More Information: PowerShell support for Power Apps (preview) Power Apps cmdlets for administrators (preview) Power Apps cmdlets for app creators (preview)
