remove-last-xamarin-refs

Author: OwenRichards1

SECURITY.md

@@ -2,7 +2,7 @@
 
 ## Security
 
-Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet) and [our GitHub organizations](https://opensource.microsoft.com/).
 
 If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
 

msal-dotnet-articles/TOC.yml

@@ -27,8 +27,6 @@
           href: acquiring-tokens/desktop-mobile/acquiring-tokens-interactively.md
         - name: Using MSAL.NET with Web Account Manager (WAM)
           href: acquiring-tokens/desktop-mobile/wam.md
-        - name: Xamarin
-          href: acquiring-tokens/desktop-mobile/mobile-applications.md
         - name: Sign-in users with social identities
           href: acquiring-tokens/desktop-mobile/social-identities.md
         - name: Integrated Windows Authentication for domain or Microsoft Entra joined machines

msal-dotnet-articles/acquiring-tokens/desktop-mobile/acquiring-tokens-interactively.md

@@ -190,13 +190,6 @@ AcquireTokenSilent(scopesForVendorApi, accounts.FirstOrDefault()).ExecuteAsync()
 
 For Microsoft personal accounts, re-prompting for consent on each native client call to authorize is the intended behavior. Native client identity is inherently insecure and the Microsoft identity platform chose to mitigate this for consumer services by prompting for consent each time the application is authorized.
 
-## Platform-specific details
-
-Depending on the platform, additional configuration might be required for interactive prompts:
-
-- [Configuration requirements and troubleshooting tips for Xamarin Android with MSAL.NET](/entra/identity-platform/msal-net-xamarin-android-considerations)
-- [Considerations for using Xamarin iOS with MSAL.NET](/entra/identity-platform/msal-net-xamarin-ios-considerations)
-
 ## Samples
 
 | Sample | Platform | Description |

msal-dotnet-articles/acquiring-tokens/desktop-mobile/mobile-applications.md

@@ -19,8 +19,6 @@ MSAL.NET can be used with authentication brokers on mobile devices, such as Micr
 To get started with MSAL.NET integration on Android, refer to the following resources:
 
 - [How to migrate Xamarin ADAL apps to MSAL for Android](/entra/identity-platform/msal-net-migration-android-broker)
-- [Xamarin Android Configuration Tips + Troubleshooting](/entra/identity-platform/msal-net-xamarin-android-considerations)
-- [Xamarin Android System Browser Info](/entra/identity-platform/msal-net-system-browser-android-considerations)
 
 To learn more about testing MSAL on Android devices, refer to the [MSAL for Android Wiki](https://github.com/AzureAD/microsoft-authentication-library-for-android/wiki/Android-Emulator-with-MSAL).
 

msal-dotnet-articles/advanced/httpclient.md

@@ -57,11 +57,6 @@ public class StaticClientWithProxyFactory : IMsalHttpClientFactory
 }
 ```
 
-
-## HttpClient and Xamarin iOS
-
-When using Xamarin iOS, it is recommended to create an `HttpClient` that explicitly uses the `NSURLSession`-based handler for iOS 7 and newer. MSAL.NET automatically creates an `HttpClient` that uses `NSURLSessionHandler` for iOS 7 and newer. For more information, read the [Xamarin iOS documentation for HttpClient](/xamarin/cross-platform/macios/http-stack).
-
 ## Troubleshooting
 
 **Problem**: On a desktop application, the authorization experience do not use the HttpClient I defined

msal-dotnet-articles/advanced/testing-apps-using-msal.md

@@ -48,7 +48,7 @@ Daemon apps use pre-deployed secrets (passwords or certificates) to talk to Micr
 For native clients, there are several approaches to testing:
 
 - Use the [Username / Password](../acquiring-tokens/desktop-mobile/username-password-authentication.md) grant to fetch a token in a non-interactive way. This flow is not recommended in production, but it is reasonable to use it for testing.
-- Use a framework, like Appium or Xamarin.Test, that provides an automation interface for both your app and the MSAL created browser.
+- Use a framework, like Appium, that provides an automation interface for both your app and the MSAL created browser.
 - MSAL exposes an extensibility point that allows developers to inject their own browser experience. The MSAL team uses this internally to test interactive auth scenarios.
 
 ## Library feedback

msal-dotnet-articles/getting-started/initializing-client-applications.md

@@ -94,14 +94,6 @@ In the code snippets using application builders, many `.With` methods can be app
 
 The modifiers you can set on a public client or confidential client application builder can be found in the `AbstractApplicationBuilder<T>` class. The different methods can be found in the [Azure SDK for .NET documentation](/dotnet/api/microsoft.identity.client.abstractapplicationbuilder-1).
 
-### Modifiers specific to Xamarin.iOS applications
-
-The modifiers you can set on a public client application builder on Xamarin.iOS are:
-
-|Modifier | Description|
-|--------- | --------- |
-|`.WithIosKeychainSecurityGroup()` | **Xamarin.iOS only**: Sets the iOS key chain security group (for the cache persistence).|
-
 ### Modifiers specific to confidential client applications
 
 The modifiers specific to a confidential client application builder can be found in the `ConfidentialClientApplicationBuilder` class. The different methods can be found in the [Azure SDK for .NET documentation](/dotnet/api/microsoft.identity.client.confidentialclientapplicationbuilder). 

msal-dotnet-articles/getting-started/scenarios.md

@@ -54,7 +54,7 @@ To enable this interaction, MSAL.NET leverages a [web browser](/azure/active-dir
 
 #### Protecting the app itself with Intune
 
-Your mobile app (written in Xamarin.iOS or Xamarin.Android) can have app protection policies applied to it, so that it can be [managed by InTune](/mem/intune/developer/app-sdk) and recognized by Intune as a managed app. The [InTune SDK](/mem/intune/developer/app-sdk-get-started) is separate from MSAL, and it talks to Microsoft Entra ID on its own.
+Your mobile app can have app protection policies applied to it, so that it can be [managed by InTune](/mem/intune/developer/app-sdk) and recognized by Intune as a managed app. The [InTune SDK](/mem/intune/developer/app-sdk-get-started) is separate from MSAL, and it talks to Microsoft Entra ID on its own.
 
 ### Desktop or service daemon app that calls a web API as itself (in its own name)