Skip to content

Commit 4cc5979

Browse files
committed
Merge remote-tracking branch 'upstream/main' into AB#7180-Error-code-0x8024402C
2 parents 40cd931 + 74b4c37 commit 4cc5979

File tree

35 files changed

+729
-446
lines changed

35 files changed

+729
-446
lines changed

Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ appliesto:
2222
- Microsoft Teams
2323
search.appverid:
2424
- MET150
25-
ms.date: 07/01/2025
25+
ms.date: 10/02/2025
2626
---
2727
# Known issues with Teams Rooms on Windows
2828

@@ -41,6 +41,7 @@ ms.date: 07/01/2025
4141
|Unable to join some Webex meetings|When you select the **Join** button to join a Cisco Webex meeting from a Teams Rooms on Windows device, you're not connected to the meeting and see the home screen on the device instead.|No workaround is available at this time. Cisco is investigating the issue.|
4242
|Only see one camera's view even though multi-camera feature is turned on.|Your Teams Rooms on Windows device is configured for multiple cameras. However after the device restarts, remote users might see only the default camera's view.<br/><br/>This issue might occur only in the first meeting after the device restarts. The cameras function as expected in all subsequent meetings.|To work around the issue, end the first meeting after the device restarts, and start a second meeting.|
4343
|Front of Room view displays a blank, black screen on a remote access tool.|When you access a Teams Rooms on Windows console remotely by using tools such as the Teams Rooms Pro Management Portal (PMP), TeamViewer, Virtual Network Computing (VNC) etc., the Front of Room (FoR) monitors display a black image instead of the expected user interface.<br/><br/>The FoR monitors in the meeting room display the expected screen but show only a black image in the view on the remote access tool.<br/><br/>If you sign in to the Teams Rooms device by using administrator credentials, you see the Windows screen in the FoR view as expected.|Restart your device to update to the latest configuration to fix the issue.|
44+
|Automatic remediation in Pro Management portal keeps failing.|The built-in remediation in the Microsoft Teams Rooms Pro Management portal to disable the USB peripheral power draining option under Windows USB settings keeps failing with the error message:<br/><br/>`Auto Remediation was unable to resolve this issue.`|To resolve the issue, implement a manual fix as described in [USB Peripheral Power Drain signal is unhealthy](./usb-peripheral-power-drain-status-unhealthy.md).|
4445

4546
## Hardware issues
4647

@@ -65,6 +66,5 @@ For issues with Teams devices offered by third-party providers, contact their in
6566
- Logitech: [Logitech Support](https://support.logi.com/hc/)
6667
- Crestron: [Crestron Support](https://support.crestron.com/)
6768
- Poly: [Poly Support](https://www.poly.com/us/support)
68-
- Yealink: [Yealink Support](https://support.yealink.com/portal/home)
6969

7070
[!INCLUDE [Third-party disclaimer](../../includes/third-party-contact-disclaimer.md)]
Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
---
2+
title: Configuring Azure Activity Log Export
3+
description: Provides guidance for resolving issues related to configuring the export of Azure activity logs
4+
ms.date: 10/01/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
8+
ms.service: azure-monitor
9+
ms.custom: I can’t configure export of activity logs
10+
---
11+
12+
# Configure Azure activity log export
13+
14+
This article outlines the steps to successfully configure Azure activity log export. This article also provides solutions to common issues that you might experience, especially if you're transitioning from older methods.
15+
16+
## Configuring activity log export
17+
18+
To configure Azure activity log export, follow these steps.
19+
20+
### Step 1: Verify current configuration
21+
22+
1. Go to the [Azure portal](https://ms.portal.azure.com/auth/login/), and access the **Activity Logs** section.
23+
1. Check the current export settings to make sure that they align with your requirements.
24+
25+
### Step 2: Update legacy methods
26+
27+
1. If you're using legacy APIs, PowerShell commands, or [log profiles](/answers/questions/1851179/what-will-happen-to-the-azure-activity-logs-soluti), update them to use diagnostic settings.
28+
1. Use the `Get-AzOperationalInsightsDataSource` command to verify existing data sources.
29+
30+
### Step 3: Configure new export settings
31+
32+
1. Select **Activity log** > **Export Activity Logs**.
33+
1. Find and select the subscription, and then select **Add diagnostic setting**.
34+
1. In the **Diagnostic setting name** box, enter a name.
35+
1. Select all applicable categories and then select **Save**.
36+
37+
> [!NOTE]
38+
> It usually takes about 30 minutes for the export to begin. For more information, see [Time before telemetry gets to destination](/azure/azure-monitor/platform/diagnostic-settings?tabs=portal#time-before-telemetry-gets-to-destination).
39+
40+
## Common issues and solutions
41+
42+
- **Issue**: Logs aren't appearing in configured destinations.
43+
- **Solution**: See the following guidance for log analytics, event hubs, and storage accounts.
44+
45+
### For log analytics
46+
47+
1. Navigate to **Log Analytics workspaces**.
48+
1. Select the workspace and then run the following query:
49+
50+
```powershell
51+
AzureActivity
52+
| summarize count() by bin(TimeGenerated,1d)
53+
```
54+
55+
This should determine the number of logs per day that are being ingested into this workspace.
56+
57+
### For event hubs
58+
59+
1. Navigate to **Event Hubs**.
60+
1. Select the event hub and then select **Data Explorer**.
61+
1. Verify the logs are reaching the event hub.
62+
63+
If the logs aren't reaching the event hub, check for throttling using a metrics blade.
64+
65+
### For storage accounts
66+
67+
1. Navigate to **Storage center | Storage accounts (Blobs)**.
68+
1. Locate and select the **insights-activity-logs** container.
69+
70+
The logs should be visible.
71+
72+
## Frequently asked questions
73+
74+
**Q1: Why don't the logs appear in the destination?**
75+
76+
**A1:** Make sure that the network is well connected, and verify the permissions for Log Analytics workspace.
77+
78+
**Q2: Why do errors appear in the PowerShell commands?**
79+
80+
**A2:** Make sure that you're using the latest Azure PowerShell module.
81+
82+
## References
83+
84+
- [Azure Monitor documentation](/azure/azure-monitor/fundamentals/overview)
85+
- [Azure activity logs overview](/azure/azure-monitor/fundamentals/data-sources)
86+
- [Configure diagnostic settings](/azure/azure-monitor/platform/diagnostic-settings?tabs=portal)
87+
88+
[!INCLUDE [azure-help-support](../../../../includes/azure-help-support.md)]

support/azure/azure-monitor/toc.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,9 @@ items:
1919
href: activity-logs/config-export/troubleshoot-permission-errors-in-activity-log-configuration.md
2020
- name: Troubleshoot the export of Activity Logs across Azure subscriptions
2121
href: activity-logs/config-export/troubleshoot-export-of-activity-logs-across-subscriptions.md
22+
- name: Configuring Azure Activity Log Export
23+
href: activity-logs/config-export/configuring-azure-activity-log-export-comprehensive-guide.md
24+
2225
- name: Application Insights
2326
items:
2427
- name: OpenTelemetry troubleshooting
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Unable to Install Astro Using a Personal Email
3+
description: Discusses why installing Apache Airflow on Astro by using a personal email account isn't supported, and how to resolve the problem.
4+
author: ProfessorKendrick
5+
ms.author: jarrettr
6+
ms.reviewer: kkendrick, v-ryanberg
7+
ms.service: partner-services
8+
ms.topic: troubleshooting-problem-resolution
9+
ms.date: 09/04/2025
10+
ai-usage: ai-assisted
11+
12+
#customer intent: As an Azure user, I want to understand why I can't install Astro by using a personal email account so that I can successfully deploy Apache Airflow.
13+
14+
---
15+
16+
# Can't install Astro using a personal email account
17+
18+
You might experience errors if you try to install Apache Airflow on Astro from the Microsoft Azure Marketplace by using a personal email account. This article explains why the errors occur and how to resolve them.
19+
20+
## Prerequisites
21+
22+
- Access to the Azure portal
23+
- An email address that's associated with a unique domain (such as work or school)
24+
- Subscription owner permissions in Azure
25+
26+
## Symptoms
27+
28+
If you try to install Apache Airflow on Astro by using a personal email account (for example, Outlook, Gmail, or Yahoo), the installation fails. Additionally, you receive an error or warning message that states that the email domain is unsupported.
29+
30+
## Cause
31+
32+
Astro installation from the Azure Marketplace doesn't support personal email accounts from generic domains. The service requires an email address that has a unique domain that's typically associated with an organization, school, or business.
33+
34+
## Solution
35+
36+
To resolve this problem, follow these steps:
37+
38+
1. Use an email address that has a unique domain (for example, your organization's email domain).
39+
2. Create a new user in Azure that has a unique domain, and assign subscription owner permissions to that user.
40+
3. Retry the Astro installation from the Azure Marketplace.
41+
42+
[!INCLUDE [Third-party contact disclaimer](../../../includes/third-party-contact-disclaimer.md)]
43+
44+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
title: Troubleshoot Astro Resource Creation in Azure
3+
description: Learn how to resolve issues when creating Astro resources in Azure, including permission and user profile requirements.
4+
author: ProfessorKendrick
5+
ms.author: jarrettr
6+
ms.reviewer: kkendrick, v-ryanberg
7+
ms.service: partner-services
8+
ms.topic: troubleshooting-problem-resolution
9+
ms.date: 09/04/2025
10+
ai-usage: ai-assisted
11+
12+
#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.
13+
---
14+
15+
# Can't create Astro resources in Azure
16+
17+
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.
18+
19+
## Prerequisites
20+
21+
- You must have `Owner` access on the Azure subscription to set up Astro integration.
22+
- Your user profile in Azure must contain all required business information.
23+
24+
## Symptoms
25+
26+
- When you try to create an Astro resource, you receive an error message that states that you're not a subscription owner.
27+
- You can't create an Astro resource because of missing details in your user profile.
28+
29+
## Cause 1: Not a subscription owner
30+
31+
Only users who have `Owner` access on the Azure subscription can set up the Astro integration.
32+
33+
### Solution 1
34+
35+
1. Verify your access level on the Azure subscription.
36+
2. If you don't have `Owner` access, ask your Azure administrator to grant you the required permissions before you start the integration setup.
37+
38+
## Cause 2: Missing details in user profile
39+
40+
Your user profile has to be updated to include key business information for Astro resource creation.
41+
42+
### Solution 2
43+
44+
1. In the Azure portal, select **Users**, and complete the required details.
45+
2. In the user information screen, search for your username.
46+
3. Edit **UserInformation** to complete all required fields.
47+
48+
## Additional troubleshooting
49+
50+
- If the deployment process takes more than three hours to complete, contact support.
51+
- If the deployment fails and the Astro resource has a status of `Failed`, delete the resource. Then, try again to create the resource.
52+
- If you receive a "DeploymentFailed" error message, check the status of your Azure subscription. Make sure that it isn't suspended and has no billing issues.
53+
54+
[!INCLUDE [Third-party contact disclaimer](../../../includes/third-party-contact-disclaimer.md)]
55+
56+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Unable to use single sign-on in Astronomer portal
3+
description: Troubleshoot issues with single sign-on (SSO) for the Astronomer portal in Azure, including consent and email requirements.
4+
author: ProfessorKendrick
5+
ms.author: jarrettr
6+
ms.reviewer: kkendrick, v-ryanberg
7+
ms.service: partner-services
8+
ms.topic: troubleshooting-problem-resolution
9+
ms.date: 09/04/2025
10+
ai-usage: ai-assisted
11+
12+
#customer intent: As an Azure administrator, I want to resolve SSO issues in Astronomer so that users can access the portal securely.
13+
14+
---
15+
16+
# Can't use single sign-on in Astronomer portal
17+
18+
This article helps you to troubleshoot and resolve issues that affect single sign-on (SSO) when you access the Astronomer portal in Microsoft Azure. If SSO isn't working, follow these steps to identify and fix common problems that are related to email, consent, and tenant settings.
19+
20+
## Prerequisites
21+
22+
- Access to the Azure subscription and Astronomer portal
23+
- Microsoft Entra account credentials
24+
- Administrator permissions to review tenant consent settings
25+
26+
## Symptoms
27+
28+
- You can't sign in to the Astronomer portal by using SSO.
29+
- You're prompted for both **Admin** and **User consent** during the initial sign-in process.
30+
- You receive error messages that are related to your email account or consent.
31+
32+
## Cause
33+
34+
SSO issues can occur if you use an incorrect email account, if you don't provide consent, or if your tenant settings prevent access.
35+
36+
## Solution
37+
38+
- Verify that you use the correct Microsoft Entra email account for SSO.
39+
- Make sure you consent to allow access for the Astronomer software-as-a-service (SaaS) portal.
40+
- If you see both **Admin** and **User consent** screens during the initial sign-in process, check your tenant consent settings.
41+
42+
[!INCLUDE [Third-party contact disclaimer](../../../includes/third-party-contact-disclaimer.md)]
43+
44+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/partner-solutions/index.yml

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,19 @@ landingContent:
2525
url: marketplace-purchases-errors.md
2626

2727
# Card
28-
- title: Informatica
28+
- title: Astro
29+
linkLists:
30+
- linkListType: how-to-guide
31+
links:
32+
- text: Can't create Astro resources in Azure
33+
url: astro/resource-creation.md
34+
- text: Can't install Astro using a personal email
35+
url: astro/personal-email.md
36+
- text: Unable to use single sign-on in Astronomer portal
37+
url: astro/single-sign-on.md
38+
39+
# Card
40+
- title: Informatica
2941
linkLists:
3042
- linkListType: how-to-guide
3143
links:

support/azure/partner-solutions/toc.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,14 @@ items:
33
href: index.yml
44
- name: Marketplace purchase errors
55
href: marketplace-purchases-errors.md
6+
- name: Astro
7+
items:
8+
- name: Can't create Astro resources in Azure
9+
href: astro/resource-creation.md
10+
- name: Can't install Astro using a personal email
11+
href: astro/personal-email.md
12+
- name: Unable to use single sign-on in Astronomer portal
13+
href: astro/single-sign-on.md
614
- name: Datadog
715
items:
816
- name: Diagnostic settings manual update

support/azure/virtual-desktop/includes/include-troubleshoot-azure-ad-joined-connections-all.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
ms.reviewer: daknappe
2+
ms.reviewer: kaushika
33
ms.topic: include
44
ms.date: 01/21/2025
55
---

support/azure/virtual-desktop/includes/include-troubleshoot-azure-ad-joined-connections-android-chrome-os.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
ms.reviewer: daknappe
2+
ms.reviewer: kaushika
33
ms.topic: include
44
ms.date: 01/21/2025
55
---

0 commit comments

Comments
 (0)