updates

Author: ProfessorKendrick

support/azure/partner-solutions/astro/personal-email.md

@@ -0,0 +1,39 @@
+---
+title: Unable to install Astro using a personal email
+description: Learn why installing Apache Airflow on Astro from the Azure Marketplace isn't supported with a personal email and how to resolve the issue.
+author: ProfessorKendrick
+ms.author: jarrettr
+ms.reviewer: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution
+ms.date: 09/04/2025
+ai-usage: ai-assisted
+
+#customer intent: As an Azure user, I want to understand why I can't install Astro with a personal email so that I can successfully deploy Apache Airflow.
+
+---
+
+# Unable to install Astro using a personal email
+
+If you're trying to install Apache Airflow on Astro from the Azure Marketplace using a personal email from a generic domain, you may encounter issues. This article explains why this happens and how to resolve it.
+
+## Prerequisites
+
+- Access to the Azure portal.
+- An email address associated with a unique domain (such as work or school).
+- Subscription owner permissions in Azure.
+
+## Symptoms
+
+- Unable to proceed with Astro installation using a personal email (for example, Gmail, Yahoo, Outlook).
+- Error or warning indicating unsupported email domain.
+
+## Cause
+
+Astro installation from the Azure Marketplace doesn't support personal emails from generic domains. The service requires an email address with a unique domain, typically associated with an organization, school, or business.
+
+## Solution
+
+1. Use an email address with a unique domain (for example, your organization's email).
+1. Alternatively, create a new user in Azure with a unique domain and assign subscription owner permissions.
+1. Retry the Astro installation from the Azure Marketplace.

support/azure/partner-solutions/astro/resource-creation.md

@@ -0,0 +1,54 @@
+---
+title: Troubleshoot Astro Resource Creation in Azure
+description: Learn how to resolve issues when creating Astro resources in Azure, including permission and user profile requirements.
+author: ProfessorKendrick
+ms.author: jarrettr
+ms.reviewer: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution
+ms.date: 09/04/2025
+ai-usage: ai-assisted
+
+#customer intent: As an Azure administrator or user, I want to resolve issues when I create Astro resources so that I can successfully set up Astro integration.
+---
+
+# Can't create Astro resource in Azure
+
+This article helps you resolve common issues that you might encounter when you try to create Astro resources in Microsoft Azure. These issues include permission errors and missing user profile information.
+
+## Prerequisites
+
+- You must have **Owner** access on the Azure subscription to set up Astro integration.
+- Make sure that your user profile in Azure contains all required business information.
+
+## Symptoms
+
+- When you try to create an Astro resource, you receive an error message that indicates that you're not a subscription owner.
+- You can't create an Astro resource because of missing details in your user profile.
+
+## Cause 1: Not a subscription owner
+
+Only users who have _Owner_ access on the Azure subscription can set up the Astro integration.
+
+### Solution 1
+
+1. Verify your access level on the Azure subscription.
+1. If you don't have **Owner** access, ask your Azure administrator to grant you the required permissions before you start the integration setup.
+
+## Cause 2: Missing details in user profile
+
+Your user profile has to be updated to include key business information for Astro resource creation.
+
+### Solution 2
+
+1. In the Azure portal, select **Users**, and fill out the required details.
+
+1. Search for your username in the user information screen.
+
+1. Edit **UserInformation** to make sure that all required fields are completed.
+
+## Additional troubleshooting
+
+- If the deployment process takes more than three hours to complete, contact support.
+- If the deployment fails and the Astro resource has a status of **Failed**, delete the resource. After deletion, try to create the resource again.
+- If you get a **DeploymentFailed error**, check the status of your Azure subscription. Make sure it isn't suspended and doesn't have any billing issues.

support/azure/partner-solutions/astro/single-sign-on.md

@@ -0,0 +1,41 @@
+---
+title: Unable to use Single sign-on in Astronomer portal
+description: "Troubleshoot issues with Single sign-on (SSO) for the Astronomer portal in Azure, including consent and email requirements."
+author: ProfessorKendrick
+ms.author: jarrettr
+ms.reviewer: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution 
+ms.date: 09/04/2025
+ai-usage: ai-assisted
+
+#customer intent: As an Azure administrator, I want to resolve SSO issues with Astronomer so that users can access the portal securely.
+
+---
+
+# Unable to use Single sign-on in Astronomer portal
+
+This article helps you troubleshoot and resolve issues with Single sign-on (SSO) when accessing the Astronomer portal in Azure. If SSO isn't working, follow the steps in this guide to identify and fix common problems related to email, consent, and tenant settings.
+
+## Prerequisites
+
+- Access to the Azure subscription and Astronomer portal.
+- Microsoft Entra account credentials.
+- Admin permissions to review tenant consent settings.
+
+## Symptoms
+
+- Unable to sign in to the Astronomer portal using SSO.
+- Prompted for both Admin and User consent during first-time login.
+- Error messages related to email or consent.
+
+## Cause
+
+SSO issues can occur if you're using an incorrect email, haven't provided consent, or tenant settings prevent access.
+
+## Solution
+
+- Verify you're using the correct Microsoft Entra email for SSO.
+- Ensure you've consented to allow access for the Astronomer SaaS portal.
+- If you see both Admin and User consent screens during first-time login, check your tenant consent settings.
+- Refer to the [single sign-on documentation](/azure/partner-solutions/astronomer/manage) for additional troubleshooting steps.