Merge pull request #227967 from pritamso/Broken-link-fix-malev

Broken link fix

Author: American-Dipper

articles/azure-app-configuration/howto-feature-filters-aspnet-core.md

@@ -22,7 +22,7 @@ The `Microsoft.FeatureManagement` library includes three feature filters:
 - `TimeWindowFilter` enables the feature flag during a specified window of time.
 - `TargetingFilter` enables the feature flag for specified users and groups.
 
-You can also create your own feature filter that implements the [Microsoft.FeatureManagement.IFeatureFilter interface](/dotnet/api/microsoft.featuremanagement.ifeaturefilter).
+You can also create your own feature filter that implements the Microsoft.FeatureManagement.IFeatureFilter interface.
 
 ## Registering a feature filter
 

articles/azure-app-configuration/index.yml

@@ -149,9 +149,9 @@ landingContent:
       - linkListType: reference
         links:
         - text: .NET Core library
-          url: /dotnet/api/microsoft.featuremanagement
+          url: https://www.nuget.org/packages/Microsoft.FeatureManagement/
         - text: .NET Core filter library
-          url: /dotnet/api/microsoft.featuremanagement.featurefilters
+          url: /dotnet/api/microsoft.azure.management.storsimple8000series.models.featurefilter
         - text: Java Spring Library
           url: https://azure.github.io/azure-sdk-for-java/springboot.html
 

articles/azure-app-configuration/quickstart-feature-flag-azure-functions-csharp.md

@@ -193,7 +193,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
 
 ## Next steps
 
-In this quickstart, you created a feature flag and used it with an Azure Functions app via the [Microsoft.FeatureManagement](/dotnet/api/microsoft.featuremanagement) library.
+In this quickstart, you created a feature flag and used it with an Azure Functions app via the [Microsoft.FeatureManagement](https://www.nuget.org/packages/Microsoft.FeatureManagement/) library.
 
 - Learn more about [feature management](./concept-feature-management.md)
 - [Manage feature flags](./manage-feature-flags.md)

articles/azure-app-configuration/use-feature-flags-dotnet-core.md

@@ -26,7 +26,7 @@ The Feature Management libraries also manage feature flag lifecycles behind the
 
 The [Add feature flags to an ASP.NET Core app Quickstart](./quickstart-feature-flag-aspnet-core.md) shows a simple example of how to use feature flags in an ASP.NET Core application. This tutorial shows additional setup options and capabilities of the Feature Management libraries. You can use the sample app created in the quickstart to try out the sample code shown in this tutorial. 
 
-For the ASP.NET Core feature management API reference documentation, see [Microsoft.FeatureManagement Namespace](/dotnet/api/microsoft.featuremanagement).
+For the ASP.NET Core feature management API reference documentation, see [Microsoft.FeatureManagement Namespace](https://www.nuget.org/packages/Microsoft.FeatureManagement/).
 
 In this tutorial, you will learn how to:
 
@@ -40,7 +40,7 @@ To access the .NET Core feature manager, your app must have references to the `M
 
 The .NET Core feature manager is configured from the framework's native configuration system. As a result, you can define your application's feature flag settings by using any configuration source that .NET Core supports, including the local *appsettings.json* file or environment variables.
 
-By default, the feature manager retrieves feature flag configuration from the `"FeatureManagement"` section of the .NET Core configuration data. To use the default configuration location, call the [AddFeatureManagement](/dotnet/api/microsoft.featuremanagement.servicecollectionextensions.addfeaturemanagement) method of the **IServiceCollection** passed into the **ConfigureServices** method of the **Startup** class.
+By default, the feature manager retrieves feature flag configuration from the `"FeatureManagement"` section of the .NET Core configuration data. To use the default configuration location, call the AddFeatureManagement method of the **IServiceCollection** passed into the **ConfigureServices** method of the **Startup** class.
 
 
 ```csharp
@@ -72,7 +72,7 @@ public class Startup
 ```
 
 
-If you use filters in your feature flags, you must include the [Microsoft.FeatureManagement.FeatureFilters](/dotnet/api/microsoft.featuremanagement.featurefilters) namespace and add a call to [AddFeatureFilters](/dotnet/api/microsoft.featuremanagement.ifeaturemanagementbuilder.addfeaturefilter) specifying the type name of the filter you want to use as the generic type of the method. For more information on using feature filters to dynamically enable and disable functionality, see [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md).
+If you use filters in your feature flags, you must include the [Microsoft.FeatureManagement.FeatureFilters](/dotnet/api/microsoft.azure.management.storsimple8000series.models.featurefilter) namespace and add a call to AddFeatureFilters specifying the type name of the filter you want to use as the generic type of the method. For more information on using feature filters to dynamically enable and disable functionality, see [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md).
 
 The following example shows how to use a built-in feature filter called `PercentageFilter`:
 
@@ -217,7 +217,7 @@ By convention, the `FeatureManagement` section of this JSON document is used for
 
 ## Use dependency injection to access IFeatureManager 
 
-For some operations, such as manually checking feature flag values, you need to get an instance of [IFeatureManager](/dotnet/api/microsoft.featuremanagement.ifeaturemanager?preserve-view=true&view=azure-dotnet-preview). In ASP.NET Core MVC, you can access the feature manager `IFeatureManager` through dependency injection. In the following example, an argument of type `IFeatureManager` is added to the signature of the constructor for a controller. The runtime automatically resolves the reference and provides an of the interface when calling the constructor. If you're using an application template in which the controller already has one or more dependency injection arguments in the constructor, such as `ILogger`, you can just add `IFeatureManager` as an additional argument:
+For some operations, such as manually checking feature flag values, you need to get an instance of IFeatureManager. In ASP.NET Core MVC, you can access the feature manager `IFeatureManager` through dependency injection. In the following example, an argument of type `IFeatureManager` is added to the signature of the constructor for a controller. The runtime automatically resolves the reference and provides an of the interface when calling the constructor. If you're using an application template in which the controller already has one or more dependency injection arguments in the constructor, such as `ILogger`, you can just add `IFeatureManager` as an additional argument:
 
 ### [.NET 5.x](#tab/core5x)
 
@@ -321,7 +321,7 @@ public IActionResult Index()
 }
 ```
 
-When an MVC controller or action is blocked because the controlling feature flag is *off*, a registered [IDisabledFeaturesHandler](/dotnet/api/microsoft.featuremanagement.mvc.idisabledfeatureshandler?preserve-view=true&view=azure-dotnet-preview) interface is called. The default `IDisabledFeaturesHandler` interface returns a 404 status code to the client with no response body.
+When an MVC controller or action is blocked because the controlling feature flag is *off*, a registered IDisabledFeaturesHandler interface is called. The default `IDisabledFeaturesHandler` interface returns a 404 status code to the client with no response body.
 
 ## MVC views
 
@@ -396,5 +396,5 @@ app.UseForFeature(featureName, appBuilder => {
 In this tutorial, you learned how to implement feature flags in your ASP.NET Core application by using the `Microsoft.FeatureManagement` libraries. For more information about feature management support in ASP.NET Core and App Configuration, see the following resources:
 
 * [ASP.NET Core feature flag sample code](./quickstart-feature-flag-aspnet-core.md)
-* [Microsoft.FeatureManagement documentation](/dotnet/api/microsoft.featuremanagement)
-* [Manage feature flags](./manage-feature-flags.md)
+* [Microsoft.FeatureManagement documentation](https://www.nuget.org/packages/Microsoft.FeatureManagement/)
+* [Manage feature flags](./manage-feature-flags.md)

articles/managed-grafana/find-help-open-support-ticket.md

@@ -16,7 +16,7 @@ In the page below, find out how you can get technical information about Azure Ma
 
 Before creating a support ticket, check out the following resources for answers and information.
 
-* [Technical documentation for Azure Managed Grafana](/index.yml): find content such as how-to guides, tutorials and the [troubleshooting guide](troubleshoot-managed-grafana.md) for Azure Managed Grafana.
+* [Technical documentation for Azure Managed Grafana](/azure/managed-grafana/): find content such as how-to guides, tutorials and the [troubleshooting guide](troubleshoot-managed-grafana.md) for Azure Managed Grafana.
 * [Microsoft Q&A](/answers/tags/249/azure-managed-grafana): browse existing questions and answers, and ask your questions around Azure Managed Grafana.
 * [Microsoft Technical Community](https://techcommunity.microsoft.com/) is the place for IT professionals and customers to collaborate, share, and learn. The website contains [Grafana-related content](https://techcommunity.microsoft.com/t5/forums/searchpage/tab/message?q=grafana).