{"loaderData":{"0-13":{"posts":[{"id":22,"slug":"how-to-programmatically-customize-site-navigation-in-wss-3","title":"HOW TO: Programmatically customize site navigation in WSS 3.0 and MOSS 2007","content":"

Note: This is a repost of an article I posted while WSS 3.0 and MOSS 2007 were in the Beta stages. The article was lost due to a server crash and many people have asked me to repost the article so I updated it with additional information, updates screen shots, and a handy little Windows Forms Application you can use to test these concepts out yourself, or build upon the code base to meet your own needs. Enjoy!

In the previous version of SharePoint the QuickLaunch menu was controlled via the ONET.XML file and ASPX pages that made up a Site Definition, and making changes to the QuickLaunch menu was a cumbersome task at best.

The new version of SharePoint provides significant improvements to the navigational elements within a SharePoint site as well as the ability to change these elements programmatically! This article describes how to programmatically interact with the navigation elements via the WSS API in order to customize SharePoint site navigation. This article also investigates the security trimming capabilities of the SharePoint UI with respect to programmatically edited navigation links.

The first thing to note is that the objects used to programmatically customize navigation reside in the Microsoft.SharePoint.Navigation namespace. So, you’ll need to add a reference to the Microsoft.SharePoint.dll in your Visual Studio projects.

New item: Controlling navigation via the SPWeb object!

The SPWeb object has been enhanced in MOSS 2007 to support the ability to control the navigation of a SharePoint site programmatically! Let’s examine how this can be done.

The SPWeb object has a new property named Navigation that returns a SPNavigation object. This object allows developers to programmatically control the navigation of a SharePoint site.

Shared Navigation Settings

One of the new settings you may apply to a site’s navigation structure is whether or not the site uses the navigation menus from its parent site.

These examples assume you have created a top level site named test and a sub site named sharednav under the test top level site as well as a sub site named nosharednav under the test top level site. Once these sites have been created their hierarchy and URLs will look like this:

$\"\"$

Before we get started, to help set the stage, here is what the navigation looks like in the test site.

$\"\"$

Here is an example of how to set a sub site to use the navigation from its parent site.

SPSite sharedNavSite = new SPSite(“http://server/test/sharednav”);

SPWeb sharedNavWeb = sharedNavSite.OpenWeb();

sharedNavWeb.Navigation.UseShared = true;

The navigation for the sharednav site looks like this after the lines of code above have been run to set the property. Notice the breadcrumb trail at the top of the page uses the breadcrumb trail for the test top level site and the horizontal menu bar uses the items from the test top level site as well.

$\"\"$

Here is an example of how to set a sub site not to use the navigation from a parent’s site.

SPSite noSharedNavSite = new SPSite(“http://server/test/nosharednav”);

SPWeb noSharedNavWeb = noSharedNavSite.OpenWeb();

noSharedNavWeb.Navigation.UseShared = false;

The navigation for the nosharednav site looks like this after the lines of code above have been run to set the property. Notice the breadcrumb trail at the top of the page uses the breadcrumb trail for the nosharednav sub site and the horizontal menu bar uses the items from the nosharednav sub site.

$\"\"$

QuickLaunch Menu Items

The QuickLaunch navigation menu may also be accessed programmatically. You can create new menu items in the QuickLaunch navigation menu and remove them. You can also specify if the link is external to the site.

Here is how you add a menu item to the QuickLaunch navigation menu.

These QuickLaunch examples assume you have created a top level site named quicklaunch.

Once this top level site has been created its URL will look like this: http://server/quicklaunch

In this example we will add two links to the QuickLaunch menu for the quicklaunch top level site, one link will be internal and one will be external. The internal link will point to the Links list in the QuickLaunch site. The external link will point to the SharePoint Experts web site.

SPSite quickLaunchSite = new SPSite(“http://server/quicklaunch”);

SPWeb quickLaunchWeb = quickLaunchSite.OpenWeb();

SPNavigationNodeCollection quickLaunchNodes = quickLaunchWeb.Navigation.QuickLaunch;

SPNavigationNode internalMenuItem = new SPNavigationNode(“Links”, “Lists/Links/AllItems.aspx”, false);

quickLaunchNodes.AddAsFirst(internalMenuItem);

SPNavigationNode externalMenuItem = new SPNavigationNode(“SharePoint Experts”, “http://www.SharePointExperts.com”, true);

quickLaunchNodes.AddAsFirst(externalMenuItem);

quickLaunchWeb.Update();

*Note: If you do not call the Update() method on the SPWeb object you are working with, you will need to reset IIS to see your changes.

Here is what the quicklaunch Site Collection looks like after the above code has been executed:

$\"\"$

Here is how you remove a menu item from the QuickLaunch navigation menu.

In this example we will remove the external link to the SharePoint Experts web site.

SPSite quickLaunchSite = new SPSite(“http://server/quicklaunch”);

SPWeb quickLaunchWeb = quickLaunchSite.OpenWeb();

SPNavigationNodeCollection quickLaunchNodes = quickLaunchWeb.Navigation.QuickLaunch;

quickLaunchNodes.Delete(quickLaunchNodes([0]));

quickLaunchWeb.Update();

Here is what the quicklaunch Site Collection looks like after the above code has been executed:

$\"\"$

Taking the QuickLaunch menu one step further

The QuickLaunch menu is capable of displaying links in a grouped fashion, as you see in the screenshot above. For example, the Lists menu item in the screenshot above has two items under it – the Calendar and Tasks links. Creating your own grouped links can be done programmatically. This is once again a simple process that requires very little code.

Here is how you add grouped menu items to the QuickLaunch navigation menu.

In this example we will create a header link for the group of links and name it Administration. Then we will add two links under the Administration header link. The links will link to the Create and Site Settings pages for the quicklaunch Site Collection.

SPSite quickLaunchSite = new SPSite(\"http://\" + serverTextBox.Text + \"/quicklaunch\");

SPWeb quickLaunchWeb = quickLaunchSite.OpenWeb();

SPNavigationNodeCollection quickLaunchNodes = quickLaunchWeb.Navigation.QuickLaunch;

SPNavigationNode internalMenuItem = new SPNavigationNode(\"Administration\", \"\", false);

quickLaunchNodes.AddAsFirst(internalMenuItem);

SPNavigationNode externalSubMenuItem1 = new SPNavigationNode(\"Site Settings\", quickLaunchWeb.Url + \"/_layouts/settings.aspx\", true);

quickLaunchNodes[0].Children.AddAsFirst(externalSubMenuItem1);

SPNavigationNode externalSubMenuItem2 = new SPNavigationNode(\"Create\", quickLaunchWeb.Url + \"/_layouts/create.aspx\", true);

quickLaunchNodes[0].Children.AddAsFirst(externalSubMenuItem2);

quickLaunchWeb.Update();

Here is what the quicklaunch Site Collection looks like after the above code has been executed:

$\"\"$

*Note: I added the Create and Site Settings links to the QuickLaunch bar to test the security trimmed aspects of the SharePoint UI. I wanted to see if SharePoint would hide these links from users who did not have access to see them because MOSS 2007 hides these links in the out of the box SharePoint UI from users who only have reader access.

I created a user named reader and granted the user read only access to the quicklaunch top level site. When I logged into the quicklaunch top level site with this user the links I just added to the QuickLaunch were available to the reader user! This is an important thing to note, and should be kept in mind when adding links to the QuickLaunch menu!

Here is what the quicklaunch Site Collection looked like when the reader user logged in:

$\"\"$

Here is the screen you see when you click one of the links you do not have access to:

$\"\"$

Top Navigation Menu Items

The top navigation menu may also be accessed programmatically. You can create new menu items in the top navigation menu navigation menu and remove them. You can also specify if the link is external to the site.

Here is how you add a menu item to the top navigation menu.

This example assumes you have created a top level site named topnavigation.

Once this Site Collection has been created its URLs will look like this: http://server/topnavigation

In this example we will add two links to the top navigation menu for the topnavigation top level site, one link will be internal and one will be external. The internal link will point to the Links list in the topnavigation site. The external link will point to the SharePoint Experts web site.

SPSite topNavigationSite = new SPSite(“http://server/topnavigation”);

SPWeb topNavigationWeb = topNavigationSite.OpenWeb();

SPNavigationNodeCollection topNavigationNodes = topNavigationWeb.Navigation.TopNavigationBar;

SPNavigationNode internalMenuItem = new SPNavigationNode(“Links”, “Lists/Links/AllItems.aspx”, false);

topNavigationNodes.AddAsFirst(internalMenuItem);

SPNavigationNode externalMenuItem = new SPNavigationNode(“SharePoint Experts”, “http://www.SharePointExperts.com”, true);

topNavigationNodes.AddAsFirst(externalMenuItem);

topNavigationWeb.Update();

Here is what the topnavigation top level site looks like after the above code has been executed:

$\"\"$

Here is how you delete a menu item from the top navigation menu. In this example we will remove the Links link we just added to the top navigation menu for the topnavigation top level site.

SPSite topNavigationSite = new SPSite(“http://server/topnavigation”);

SPWeb topNavigationWeb = topNavigationSite.OpenWeb();

SPNavigationNodeCollection topNavigationNodes = topNavigationWeb.Navigation.TopNavigationBar;

topNavigationNodes.Delete(topNavigationNodes[0]);

topNavigationWeb.Update();

Here is what the topnavigation top level site looks like after the above code has been executed:

$\"\"$

Taking the Top Navigation one step further

The top Navigation menu is capable of displaying dropdown menus that consist of multiple items. Adding additional sub menu items under the topmost item is a simple process and requires very little code.

Here is how you add a sub menu item to a top level menu item in the top navigation menu. In this example we will add a new top level menu item to the top navigation menu that has two sub menu items under it for the topnavigation top level site.

SPSite topNavigationSite = new SPSite(“http://server/topnavigation”);

SPWeb topNavigationWeb = topNavigationSite.OpenWeb();

SPNavigationNodeCollection topNavigationBarNodes =

topNavigationWeb.Navigation.TopNavigationBar;

SPNavigationNode headerMenuItem = new SPNavigationNode(\"SharePoint Sites\", \"\", false);

topNavigationBarNodes.AddAsFirst(headerMenuItem);

SPNavigationNode externalSubMenuItem1 = new SPNavigationNode(\"SharePoint Experts\", \"http://www.SharePointExperts.com\", true);

topNavigationBarNodes[0].Children.AddAsFirst(externalSubMenuItem1);

SPNavigationNode externalSubMenuItem2 = new SPNavigationNode(\"SharePoint University\", \"http://www.SharePointU.com\", true);

topNavigationBarNodes[0].Children.AddAsFirst(externalSubMenuItem2);

topNavigationWeb.Update();

Here is what the topnavigation top level site looks like after the above code has been executed:

$\"\"$

*Note: I was curious to see if the Top Navigation menu reacted the same way the QuickLaunch menu bar did regarding the security trimming of the UI. So I created an Administration Header link and two sub links for the Create and Site Settings pages.

I granted the reader user read only access to the topnavigation top level site and when I logged into the topnavigation top level site with this user the links I just added to the Top Navigation menu were available to the reader user! This is an important thing to note, and should be kept in mind when adding links to the Top Navigation menu!

Here is the code I used to add the links:

SPSite topNavigationSite = new SPSite(“http://server/topnavigation”);

SPWeb topNavigationWeb = topNavigationLaunchSite.OpenWeb();

SPNavigationNodeCollection topNavigationBarNodes =

topNavigationWeb.Navigation.TopNavigationBar;

SPNavigationNode headerMenuItem = new SPNavigationNode(\"Administration\", \"\", false);

topNavigationBarNodes.AddAsFirst(headerMenuItem);

SPNavigationNode externalSubMenuItem1 = new SPNavigationNode(\"Site Settings\", topNavigationWeb.Url + \"/_layouts/settings.aspx\", true);

topNavigationBarNodes[0].Children.AddAsFirst(externalSubMenuItem1);

SPNavigationNode externalSubMenuItem2 = new SPNavigationNode(\"Create\", topNavigationWeb.Url + \"/_layouts/create.aspx\", true);

topNavigationBarNodes[0].Children.AddAsFirst(externalSubMenuItem2);

topNavigationWeb.Update();

Here is what the topnavigation top level site looked like when the administrator or the reader user user logged in; the links appear for both users.

$\"\"$

I created a handy little Windows Forms Application you can use to test these concepts out yourself, or build upon the code base to meet your own needs. The application is easy to use, just enter the name of your SharePoint server, then click the buttons from top to bottom and follow along with this article. The application looks like this:

$\"\"$

I hope this article and the application come in handy for you! Now, it’s time to go skiing! :)

","excerpt":"","date":"2007-12-27T01:36:00","modified":"2013-07-01T20:05:51","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":97,"name":"SharePoint","slug":"sharepoint","count":58},{"id":84,"name":"SharePoint 2007","slug":"sharepoint-2007","count":22}],"tags":[{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":6,"name":"HOW TO: SharePoint","slug":"how-to-sharepoint","count":31},{"id":15,"name":"QuickLaunch","slug":"quicklaunch","count":1},{"id":7,"name":"SharePoint","slug":"sharepoint","count":85},{"id":16,"name":"Top Navigation","slug":"top-navigation","count":1}],"status":"publish"}],"total":1,"totalPages":1,"currentPage":1,"archiveType":"tag","archiveName":"Top Navigation","archiveSlug":"top-navigation","archivePathSegments":"top-navigation","categories":[{"id":146,"name":"AI","slug":"ai","count":1},{"id":90,"name":"Blog","slug":"blog","count":2},{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":102,"name":"Community","slug":"community","count":41},{"id":110,"name":"GitHub","slug":"github","count":4},{"id":139,"name":"Lacrosse","slug":"lacrosse","count":1},{"id":96,"name":"Mobile","slug":"mobile","count":62},{"id":46,"name":"Most Popular","slug":"most-popular","count":19},{"id":88,"name":"Office","slug":"office","count":21},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":89,"name":"Operations","slug":"operations","count":13},{"id":121,"name":"PowerApps","slug":"powerapps","count":57},{"id":87,"name":"Publications","slug":"publications","count":17},{"id":97,"name":"SharePoint","slug":"sharepoint","count":58},{"id":84,"name":"SharePoint 2007","slug":"sharepoint-2007","count":22},{"id":98,"name":"SharePoint 2010","slug":"sharepoint-2010","count":40},{"id":99,"name":"SharePoint 2013","slug":"sharepoint-2013","count":20},{"id":106,"name":"SharePoint 2016","slug":"sharepoint-2016","count":6},{"id":118,"name":"SharePoint Framework","slug":"sharepoint-framework","count":1},{"id":83,"name":"Speaking Engagements","slug":"speaking-engagements","count":41},{"id":119,"name":"SPFx","slug":"spfx","count":1},{"id":85,"name":"SPS Events Mobile","slug":"sps-events-mobile","count":4},{"id":116,"name":"Teams","slug":"teams","count":3},{"id":1,"name":"Uncategorized","slug":"uncategorized","count":3},{"id":86,"name":"Windows 8","slug":"windows-8","count":7},{"id":101,"name":"Azure","slug":"azure","count":24},{"id":100,"name":"BCS","slug":"bcs","count":26},{"id":132,"name":"CDS","slug":"cds","count":3},{"id":120,"name":"Flow","slug":"flow","count":18}],"tags":[{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":7,"name":"SharePoint","slug":"sharepoint","count":85},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":45,"name":"O365","slug":"o365","count":65},{"id":112,"name":"PowerApps","slug":"powerapps","count":56},{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":26,"name":"SharePoint 2010","slug":"sharepoint-2010","count":32},{"id":6,"name":"HOW TO: SharePoint","slug":"how-to-sharepoint","count":31},{"id":57,"name":"Mobility","slug":"mobility","count":28},{"id":3,"name":"Conferences","slug":"conferences","count":27},{"id":41,"name":"Azure","slug":"azure","count":21},{"id":4,"name":"BDC","slug":"bdc","count":20},{"id":40,"name":"Windows Phone 7","slug":"windows-phone-7","count":17},{"id":58,"name":"Android","slug":"android","count":14},{"id":60,"name":"iPad","slug":"ipad","count":14},{"id":68,"name":"SharePoint 2013","slug":"sharepoint-2013","count":14},{"id":23,"name":"Conference Materials","slug":"conference-materials","count":13},{"id":59,"name":"iPhone","slug":"iphone","count":13},{"id":113,"name":"Flow","slug":"flow","count":12},{"id":43,"name":"SharePoint Online","slug":"sharepoint-online","count":12},{"id":28,"name":"BCS","slug":"bcs","count":11},{"id":80,"name":"Windows Phone 8","slug":"windows-phone-8","count":8},{"id":61,"name":"iOS","slug":"ios","count":7},{"id":38,"name":"Magazine Articles","slug":"magazine-articles","count":7},{"id":74,"name":"SharePoint Apps","slug":"sharepoint-apps","count":7},{"id":9,"name":"Workflow","slug":"workflow","count":7},{"id":22,"name":"Development Utilities","slug":"development-utilities","count":6},{"id":37,"name":"MSDN","slug":"msdn","count":6},{"id":25,"name":"Silverlight","slug":"silverlight","count":6},{"id":8,"name":"Virtual Environments","slug":"virtual-environments","count":5},{"id":30,"name":"External Content Types","slug":"external-content-types","count":4},{"id":72,"name":"SharePoint Hosted","slug":"sharepoint-hosted","count":4},{"id":13,"name":"Site Definitions","slug":"site-definitions","count":4},{"id":12,"name":"Site Templates","slug":"site-templates","count":4},{"id":44,"name":"SPO","slug":"spo","count":4},{"id":33,"name":"Visual Studio","slug":"visual-studio","count":4},{"id":55,"name":"WCM","slug":"wcm","count":4},{"id":128,"name":"CDS","slug":"cds","count":3},{"id":127,"name":"Ignite","slug":"ignite","count":3},{"id":115,"name":"SPFx","slug":"spfx","count":3},{"id":14,"name":"SSO","slug":"sso","count":3},{"id":117,"name":"Teams","slug":"teams","count":3},{"id":24,"name":"Hyper-V","slug":"hyper-v","count":2},{"id":126,"name":"IoT","slug":"iot","count":2},{"id":76,"name":"Mapping","slug":"mapping","count":2},{"id":56,"name":"Outlook","slug":"outlook","count":2},{"id":32,"name":"Sandbox","slug":"sandbox","count":2},{"id":21,"name":"SharePoint Certified Architect","slug":"sharepoint-certified-architect","count":2},{"id":11,"name":"SharePoint Designer","slug":"sharepoint-designer","count":2},{"id":108,"name":"SharePoint Framework","slug":"sharepoint-framework","count":2},{"id":34,"name":"Visual Web Parts","slug":"visual-web-parts","count":2},{"id":91,"name":"Xamarin","slug":"xamarin","count":2},{"id":27,"name":".NET Assembly Connector","slug":"net-assembly-connector","count":1},{"id":50,"name":"Access Services","slug":"access-services","count":1},{"id":35,"name":"Aptillon","slug":"aptillon","count":1},{"id":36,"name":"BCS FAQ","slug":"bcs-faq","count":1},{"id":39,"name":"Books","slug":"books","count":1},{"id":148,"name":"Claude","slug":"claude","count":1},{"id":131,"name":"Common Data Service","slug":"common-data-service","count":1},{"id":82,"name":"Community","slug":"community","count":1},{"id":52,"name":"Composites","slug":"composites","count":1},{"id":123,"name":"Containers","slug":"containers","count":1},{"id":92,"name":"Cordova","slug":"cordova","count":1},{"id":65,"name":"CSS3","slug":"css3","count":1},{"id":140,"name":"DIY","slug":"diy","count":1},{"id":124,"name":"Docker","slug":"docker","count":1},{"id":133,"name":"Flows","slug":"flows","count":1},{"id":75,"name":"Geolocation","slug":"geolocation","count":1},{"id":111,"name":"GitHub","slug":"github","count":1},{"id":125,"name":"HOW TO: Flow","slug":"how-to-flow","count":1},{"id":62,"name":"HTML5","slug":"html5","count":1},{"id":49,"name":"InfoPath Forms Services","slug":"infopath-forms-services","count":1},{"id":64,"name":"JavaScript","slug":"javascript","count":1},{"id":63,"name":"JQuery","slug":"jquery","count":1},{"id":66,"name":"JQuery Mobile","slug":"jquery-mobile","count":1},{"id":31,"name":"Lists","slug":"lists","count":1},{"id":69,"name":"Mashups","slug":"mashups","count":1},{"id":19,"name":"MCA","slug":"mca","count":1},{"id":18,"name":"MCM","slug":"mcm","count":1},{"id":79,"name":"Nofifications","slug":"nofifications","count":1},{"id":105,"name":"Office","slug":"office","count":1},{"id":95,"name":"Office Add-ins","slug":"office-add-ins","count":1},{"id":78,"name":"Office Web Apps Server","slug":"office-web-apps-server","count":1},{"id":130,"name":"Operations","slug":"operations","count":1},{"id":129,"name":"PowerShell","slug":"powershell","count":1},{"id":15,"name":"QuickLaunch","slug":"quicklaunch","count":1},{"id":29,"name":"Search","slug":"search","count":1},{"id":107,"name":"SharePoint 2016","slug":"sharepoint-2016","count":1},{"id":71,"name":"SharePoint App","slug":"sharepoint-app","count":1},{"id":20,"name":"SharePoint Certified Master","slug":"sharepoint-certified-master","count":1},{"id":17,"name":"SharePoint Master Certification","slug":"sharepoint-master-certification","count":1},{"id":109,"name":"SharePoint Mobile App","slug":"sharepoint-mobile-app","count":1},{"id":77,"name":"SharePoint Saturday","slug":"sharepoint-saturday","count":1},{"id":73,"name":"SP APP","slug":"sp-app","count":1},{"id":70,"name":"SPAPP","slug":"spapp","count":1},{"id":81,"name":"SPS Events","slug":"sps-events","count":1},{"id":67,"name":"SSS","slug":"sss","count":1},{"id":16,"name":"Top Navigation","slug":"top-navigation","count":1},{"id":94,"name":"Training","slug":"training","count":1},{"id":134,"name":"Twitter","slug":"twitter","count":1},{"id":93,"name":"Universal","slug":"universal","count":1},{"id":114,"name":"Windows Phone","slug":"windows-phone","count":1},{"id":51,"name":"Workflows","slug":"workflows","count":1},{"id":53,"name":"WP7; SharePoint; SharePoint 2010; Social; Mobile","slug":"wp7-sharepoint-sharepoint-2010-social-mobile","count":1},{"id":147,"name":"XCode","slug":"xcode","count":1}],"recentPosts":[{"id":2222,"slug":"how-to-reauthenticate-claude-in-xcode","title":"HOW TO: Reauthenticate Claude in XCode","content":"\n

If you set up XCode to integrate with Claude you may find the OAuth token expires and the chat in XCode cannot communicate with Claude, then you see this error message.

OAuth token has expired. Please obtain a new token or refresh your existing token.

\n\n\n\n

\n\n\n\n

To resolve this issue quickly open XCode Settings > Intelligence.

\n\n\n\n

Click the ellipses next to your account, and select Sign Out.

\n\n\n\n

\n\n\n\n

Click the ellipses again and select Sign In.

\n\n\n\n

This will open a web browser where you can sign in and click Authorize.

\n\n\n\n

Restart XCode.

\n\n\n\n

\n\n\n\n

Happy coding!

\n","excerpt":"

If you set up XCode to integrate with Claude you may find the OAUth token expires and the chat in XCode cannot communicate with Claude. Here's how to fix it.

","date":"2026-04-01T21:22:55","modified":"2026-04-01T21:22:57","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":146,"name":"AI","slug":"ai","count":1}],"tags":[{"id":148,"name":"Claude","slug":"claude","count":1},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":147,"name":"XCode","slug":"xcode","count":1}],"featuredImage":"/blog/uploads/2026/04/xcode-claude.png","status":"publish"},{"id":2165,"slug":"how-to-disable-turn-off-a-power-platform-managed-environment","title":"HOW TO: Disable/Turn Off a Power Platform Managed Environment","content":"\n

What do you do if you accidentally enabled a Managed Environment in the Power Platform and you want to make the Environment non-Managed again? There is no way in the Power Platform Admin Center to Disable / Turn Off a Managed Environment, you can only Enable or Delete Managed Environments in the Admin Center. To Disable / Turn Off a Managed Environment, and go back to a non-Managed Environment, you must use PowerShell. Here's how to do it:

\n\n\n\n

Open a PowerShell prompt as Administrator.

\n\n\n\n

Install PowerShell

\n\n\n\n

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell

\n\n\n\n

Log in with an account that has permissions to administer Environments. The following command will open an authentication prompt. The prompt supports MFA.

\n\n\n\n

Add-PowerAppsAccount -Endpoint prod

\n\n\n\n

Run this code that sets protectionLevel to Basic, which turns an Environment from Managed to non-Managed.

\n\n\n\n

$UpdatedGovernanceConfiguration = [pscustomobject]@{ protectionLevel = \"Basic\" }

\n\n\n\n

Run this command to apply the changes to the Environment you want to convert from Managed to non-Managed. Make sure to replace the Environment Id accordingly.

\n\n\n\n

Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName -UpdatedGovernanceConfiguration $UpdatedGovernanceConfiguration

\n\n\n\n

Here's what it all looks like:

\n\n\n\n

\n\n\n\n

Here's the Microsoft documentation that describes part of this process.

\n\n\n\n

https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-enable#disable-managed-environments-using-powershell

\n\n\n\n

\n","excerpt":"

What do you do if you accidentally enabled a Managed Environment in the Power Platform and you want to make the Environment non-Managed again?

","date":"2024-10-15T16:47:48","modified":"2024-10-15T16:47:49","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":112,"name":"PowerApps","slug":"powerapps","count":56}],"featuredImage":"/blog/uploads/2024/10/sunset-ocean.jpg","status":"publish"},{"id":2143,"slug":"how-to-make-a-diy-lacrosse-goal-transporter","title":"HOW TO: Make a DIY lacrosse goal transporter","content":"\n

There are several products on the market that make it easy to move your lacrosse goal. I investigated them and then created my own to save my yard, my back, and my money. An added bonus is you can store your goal on the transporter to keep it off the ground and free from dirt and moisture.

\n\n\n\n

This is especially helpful if you have ECD targets, a Smart Backstop shooting net, and a Lax Dog strapped to your goal, which makes it quite heavy! These are not affiliate links, I don't make any money off them. Just thought I'd share the links because we really enjoy these products.

\n\n\n\n

Hopefully this article helps out my brothers and sisters in the lax community.

\n\n\n\n

\n\n\n\n

Parts

\n\n\n\n

1 - 4x4x8' #2 Ground Contact Green pressure-treated timber - $10.30

\n\n\n\n

1 - 2x4x8' #2 Ground Contact Green pressure treated lumber - $3.89

\n\n\n\n

1 - 21\" #2 Ground Contact Green pressure-treated timber - $0.00 *

\n\n\n\n

19 - #9 2 1/2\" coated deck screws - $0.00 *

\n\n\n\n

2 - 5/8\" x 8\" galvanized lag screws - $3.39 (these become the wheel axles)

\n\n\n\n

2 - 8\" Pneumatic Utility Tire (no flat) - $20.57 (comes with plastic spacers - you could cut a small pipe to make a spacer too)

\n\n\n\n

* Already had these items in my shop from previous projects.

\n\n\n\n

Total: $38.15

\n\n\n\n

Instructions

\n\n\n\n

Lay the goal on top of the 4x4.

\n\n\n\n

Mark the 4x4 where you want to cut it. Leave a little room on the ends to install a stopper (scroll down to see the picture with the stopper) to prevent the goal from sliding off the end. I left about 2\" of space on either side of the goal.

\n\n\n\n

Cut the 4x4 to the length that makes sense for your goal. I went with 80\" for my 4x4.

\n\n\n\n

Mark the center of each end of the 4x4. Then use a 7/16\" (or the appropriate size bit that is small enough that the threads on the lag screw will still bite into the wood) drill bit to drill a hole as deep as the threads on your lag screw. The lag screws are the axles for the wheels. In my case I used a boring bit, and the hole was over 4\" deep. This is the most important step. If you drill this hole off-center or off-axis the tires will not be aligned properly. If the pressure treated wood is fresh and wet, this could be challenging. Take your time, get it right the first time.

\n\n\n\n

Use a large socket wrench to screw the lag screws into the 4x4 until all the threads are engaged. Don't put your wheel or spacer on yet. Leave them off so you can concentrate on screwing in the screw perfectly. This is the 2nd most important step. If you screw it in on an angle, the tires will not be aligned properly. This is not easy; you will need to put a lot of muscle into this.

\n\n\n\n

Use a large socket wrench to un-screw the lag screws from the 4x4 all the way. Be careful when you take out the lag screw, it could be quite hot from the friction.

\n\n\n\n

Lay the goal on top of the 4x4 and center it.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Cut some of the 21\" 2x4 to make little stoppers for top ends of the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Align the stopper on top of the 4x4 and drill holes in the 2x4 stopper you just made. Go all the way through so you mark the 4x4 with holes. Remove the stopper and finish drilling out the holes in the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Screw the stoppers to the 4x4 with the deck screws. You will do this 2 times, one for each end.

\n\n\n\n

Cut some 2x4 to make a brace for the goal posts to prevent the goal from sliding off the 4x4. I made my braces 8\" long. You will do this 2 times, one for each goal post.

\n\n\n\n

Align the brace on the side of the 4x4 and drill holes in the 2x4 braces you just made. Go all the way through so you mark the 4x4 with holes. Remove the brace and finish drilling out the holes in the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Screw the brace to the 4x4 with the deck screws. You will do this 2 times, one for each end.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Align the 2x4 in the middle of the 4x4 make the end flush to the edge of the 4x4. Drill holes in the 2x4 and go all the way through so you mark the 4x4 with holes. Remove the brace and finish drilling out the holes in the 4x4.

\n\n\n\n

Screw the 2x4 to the 4x4 with the deck screws.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Pass the lag screw through the wheel, add the spacer on the other side, then use the large socket wrench to tighten the screw. You will do this 2 times, one for each end.

\n\n\n\n

Walk around the back of your goal and grab the 2x4 and lift up the goal.

\n\n\n\n

\n\n\n\n

Now, add a little flair and make it easier to lift the 2x4 by adding a custom handle. This beauty was made by my Dad when he created our treehouse when I was a boy. It lives on today as part of our lacrosse transporter! I attached it with 2 deck screws.

\n\n\n\n

\n\n\n\n

Move your goal to a suitable location and rip some Gs!

\n\n\n\n

\n\n\n\n

Here are some more pictures that show everything from a few different angles.

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n","excerpt":"

There are several products on the market that make it easy to move your lacrosse goal. I investigated them and then created my own to save my yard, my back, and my money.

","date":"2024-09-23T22:29:27","modified":"2024-11-20T16:48:07","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":139,"name":"Lacrosse","slug":"lacrosse","count":1}],"tags":[{"id":140,"name":"DIY","slug":"diy","count":1}],"featuredImage":"/blog/uploads/2024/09/fi.jpg","status":"publish"},{"id":2117,"slug":"accelerate-development-with-the-catalog-for-power-platform","title":"Accelerate development with the Catalog for Power Platform","content":"\n

This video demonstrates how to accelerate development with the Catalog for Power Platform in both green field (creating a new app from scratch) and enhancement (taking an existing app and updating it) scenarios.

\n\n\n\n

In this video you will learn how to add Solutions to the Catalog and how to deploy them to Power Platform environments. You will also learn how to organize your Solutions and reusable components to enable quick app development and streamlined enhancements and maintenance.

\n\n\n\n

\n","excerpt":"

Learn how to accelerate development with the Catalog for Power Platform in both green field (creating a new app from scratch) and enhancement (taking an existing app and updating it) scenarios.

","date":"2023-05-25T13:30:00","modified":"2023-05-25T17:49:54","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66}],"featuredImage":"/blog/uploads/2019/08/succulent-garden.jpg","status":"publish"},{"id":2125,"slug":"what-is-the-catalog-for-power-platform","title":"What is the Catalog for Power Platform?","content":"\n

In this video you will learn the basics about the Catalog for Power Platform and how the Catalog for Power Platform accelerates development and promotes consistency by making it easy for makers to discover and reuse Power Platform components.

\n\n\n\n

After you watch this video, check out these other great videos about the Catalog for Power Platform and related concepts.

\n\n\n\n

Accelerate development with the Catalog for Power Platform

\n\n\n\n

Sharing PCF Components with the Catalog in Power Platform

\n\n\n\n

Power Platform ALM - Choose the Right Approach

\n\n\n\n

\n","excerpt":"

Learn the basics about the Catalog for Power Platform and how the Catalog for Power Platform accelerates development.

","date":"2023-05-25T13:30:00","modified":"2023-05-25T17:52:48","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":112,"name":"PowerApps","slug":"powerapps","count":56}],"featuredImage":"/blog/uploads/2018/01/Ducks-Little-Miami.jpg","status":"publish"}]}},"actionData":null,"errors":null}

TagTop Navigation

HOW TO: Programmatically customize site navigation in WSS 3.0 and MOSS 2007