Need Entra ID + Teams tenant for demo environment — Dev Program signup failing (Error 50001)

Question

Hi,

I'm trying to set up a demo/qa environment that requires Microsoft Entra ID and Teams ingestion via the Microsoft Graph API.

Current tenant state:

• Tenant ID: [Moderator note: personal info removed]
• Licensed products: Office 365 E3 (1 license), Microsoft 365 Business Basic (3 licenses)
• Entra ID plan shown under Licensed Features: "Microsoft Entra ID for Office 365"
• No Entra ID P1 or P2 active

What is failing:

We have a multi-tenant Azure app that ingests data from the Microsoft Graph API. This app works successfully against 4 other tenants. When targeting this tenant, we get 403 Forbidden on endpoints like https://graph.microsoft.com/beta/auditLogs/signIns. Admin consent has been granted for the app in this tenant.

We believe the issue is that "Entra ID for Office 365" does not include access to sign-in/audit log APIs, which require at least Entra ID P1.

Dev Program signup issue:

I attempted to create an M365 Developer tenant (which includes E5 licenses) through the Microsoft 365 Developer Program, but the signup consistently fails during phone verification with:

Code: 50001

MS-CorrelationId: [Moderator note: personal info removed]

What I need help with:

1. Is there a way to resolve the Developer Program signup error (50001)?
2. What are my options for getting a tenant with Entra ID P1+ capabilities for a demo environment?

Thank you.

Answer 1

Please note that Q&A forum is a public platform, and moderators will modify the question to hide personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Hi @Dylan Parker

Thank you for reaching out to the Q&A Forum.

Based on the information you shared, I understand that you are trying to set up a demo/QA environment that requires Microsoft Entra ID and Microsoft Graph API access (specifically for Teams ingestion and audit log endpoints). However, the tenant you are testing with only has Office 365 E3 and Microsoft 365 Business Basic licenses, which provide Microsoft Entra ID for Office 365 (essentially the Free tier). As a result, your application receives 403 Forbidden errors when calling endpoints such as /beta/auditLogs/signIns, even though admin consent has already been granted. Additionally, when attempting to create a Microsoft 365 Developer tenant, the signup process fails during phone verification with error code 50001.

Regarding the Developer Program signup error (50001): This error commonly occurs during the phone verification step of the Microsoft 365 Developer Program registration. In many cases, it happens when the phone number has already been associated with another Developer Program account or has reached the allowed verification limit. One possible workaround is to remove the existing Developer Program profile associated with that phone number or attempt the signup process using a completely different phone number. You may refer to the official Microsoft 365 Developer Program FAQ for additional details on verification requirements.

If using a new phone number still results in the same error, the appropriate next step would be to contact Microsoft Developer Support. Support requests related to the Developer Program are typically handled through the Services Hub. Please note that access to the Services Hub depends on your organization’s support agreement and may require a paid support plan. You can review the requirements and sign-in conditions in the Services Hub sign-in FAQs before submitting a request.

Regarding the 403 errors when accessing Graph endpoints such as auditLogs/signIns: The Microsoft Graph audit and sign-in log APIs require Microsoft Entra ID P1 or P2 licensing. Since the tenant currently only includes Entra ID Free (via Office 365 licensing), the backend service may block these endpoints even if the application permissions and admin consent are correctly configured.

To enable those APIs in your demo environment, you may consider the following options:

1. Upgrade the tenant with Microsoft Entra ID P1 or P2 licenses and assign them to the relevant users.
2. Use a Microsoft 365 Developer tenant with E5 licenses, which already includes advanced Entra ID capabilities suitable for development and testing scenarios.

I hope this information helps clarify the situation.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

1. Resolving the Microsoft 365 Developer Program signup error (50001)

The context does not provide specific remediation steps for error 50001 during Microsoft 365 Developer Program phone verification. However, it does define the supported sign-in methods and the general signup flow, which can be used to validate the basics:

• Only supported sign-in identities can be used to join the program:
  • A Microsoft account or a Microsoft Entra–enabled email.
  • Phone-number-only accounts and *.onmicrosoft.com accounts are not supported for sign-in to the Developer Program portal. If one of these is used, signup fails and a supported account must be used instead.
• The documented steps to join are:
  1. Go to the "Join the Microsoft 365 Developer Program" page.
  2. Sign in with a supported Microsoft account or Microsoft Entra–enabled email (not phone number, not *.onmicrosoft.com).
  3. Choose Join now and complete the signup form and preferences.

Given this, the first checks are:

• Ensure the account used to sign in to the Developer Program is not:
  • A phone-number-based account.
  • An *.onmicrosoft.com account.
• If a Visual Studio subscription exists, join via the Visual Studio membership portal as recommended, then follow the documented join flow.

If signup still fails after using a supported account and following the documented flow, the next step is to contact Microsoft support, as the context shows that contacting support is the escalation path for account/tenant issues and for talking to a human when self-service flows fail.

2. Options to get a tenant with Entra ID P1+ capabilities for a demo environment

The context provides several supported options to obtain a tenant suitable for development and demo scenarios, including tenants that come with Entra ID P1/P2 capabilities:

1. Microsoft 365 Developer Program (E5 developer subscription)

• Joining the Microsoft 365 Developer Program provides a sandbox tenant with E5 licenses, configured users, groups, and mailboxes.
• The E5 licenses in this context include Microsoft Entra ID P2 licenses when using the Microsoft 365 Developer Program sandbox tenant created via the documented flow for Entra Verified ID development.
• This tenant is explicitly intended for development and testing and is the primary recommended path when eligible.

2. Free Microsoft Entra tenant via Azure free account

• Create a new Microsoft Entra tenant with an Azure free account using the documented "Create a new tenant" flow.
• This provides the Entra ID Free tier initially.
• After creation, a free trial of Microsoft Entra ID P1 or P2 can be activated for testing, as documented.
• This combination (Azure free account + Entra ID P1/P2 trial) yields a tenant with P1/P2 capabilities suitable for development and demo workloads.

3. Education-focused demo tenants (if the scenario fits)

• For education solutions (Teams EDU, School Data Sync, etc.), there are two additional options:
  • Demo EDU development tenant: a developer tenant for building and testing education solutions that integrate with Microsoft Teams and other EDU services.
  • Demo EDU tenant: a fully functional Microsoft 365 environment for demos and personal development.
• These require joining the Microsoft Partner Network and then requesting an EDU development tenant via the documented Partner Sign Up flow.

4. Entra Verified ID developer setup (as a pattern)

• The Entra Verified ID developer guidance describes two supported ways to get a development tenant:
  • Microsoft 365 Developer Program sandbox tenant with E5 (includes Entra ID P2).
  • Free Entra tenant via Azure free account plus optional P1/P2 trial.
• The same patterns apply to other Graph-based development scenarios that require P1/P2 features.

Summary of practical options for a P1+/P2-capable demo tenant:

• Option A: Resolve the Developer Program signup issue by using a supported sign-in identity (not phone-number-only, not *.onmicrosoft.com) and complete the Microsoft 365 Developer Program flow to obtain an E5 developer tenant with Entra ID P2.
• Option B: Create a new Entra tenant using an Azure free account, then activate a free Entra ID P1 or P2 trial in that tenant for development and testing.
• Option C (if applicable): For education scenarios, join the Microsoft Partner Network and request a demo EDU development tenant or demo EDU tenant.

---

References:

• Microsoft Entra service description
• Microsoft Entra Verified ID developer information
• Introduction to Microsoft Entra tenants
• Set up a demo tenant to develop education solutions
• Welcome to the Microsoft 365 Developer Program
• Set up an EDU development environment