The Baretta

What Environment Variables are a great way to manage your solutions as they pass through DEV/TEST/PROD environments.  They save having to manually update flows/apps during each change and test iteration. However there is a gotcha to understand when you're planning your next migration or app update. More on Environment Variables | Microsoft Learn Why The two issues I faced using Environment Variables were due to the ' Current Value '. Issue #1 : If you don't want the value you used in DEV to push through to TEST/PROD, you need to remove the 'Current Value' from your solution BEFORE exporting it. If this is not done, and you're migrating as a  managed  solution, the 'Current Value' will flow through to your TEST environment, and cannot be changed because the solution is locked down. When a single sentence in an MS Learn article can cause so much pain... Issue #2 : If you're like me and you realised this AFTER you'd already imported into another...

Even if the Yammer Group was created first... So yeah, don't delete O365 Groups unless you want everything gone. If you need to recover: ##Do this off Network with regular powershell opened as Administrator Import-Module AzureADPreview Connect-AzureAD Get-AzureADMSDeletedGroup | Out-GridView Restore-AzureADMSDeletedDirectoryObject –Id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Get-AzureADGroup –ObjectId xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Update - 08/12/2017 Microsoft are rolling this restore functionality into Exchange Online over the next month or two, so you wont need the script above soon:

PURPOSE Ever wondered what sort of SQL data connections are possible in SharePoint Online? Ever wondered of the limitations when trying this type of setup? If so, read on...  This tutorial will go over all the steps to setup everything from scratch.  Every step is important, you miss one, it won't work. WHAT YOU NEED SharePoint Online Plan 2 (you cannot achieve this with the basic version of SharePoint online as you require access to the Admin panel to setup Secure Store access permissions and BCS permissions. A windows azure account (which you can get a free 30 day trial as long as you're willing to provide your credit card. SharePoint Designer 2013 installed locally (required to create the final connection to the azure DB. Please note, you'll make this a hell of a lot easier if all these accounts are setup using the same office logon.  Otherwise you'll be logging in and out like a madman. IMPLEMENTATION Step 1 - Create SQL Database:   ...