Microsoft for Startups rejected my verified business because my LinkedIn account was too new — after four months of verification issues

I'm a South Korean startup founder operating ModuVoice (https://moduvoice.com), an AI-based speech technology service.

I've been trying to resolve a Microsoft for Startups verification issue since June 2026, and I'm sharing my experience because I believe it raises important questions about the program's verification process.

Here's what happened:

• June: My business verification failed. Microsoft Support subsequently acknowledged an internal system issue preventing Business Verification reviews and manual intervention.

September: My initial $1,000 Azure startup credits had expired, and I opened another support case to resolve the verification issue.

October: I submitted my official South Korean business registration certificate, GitHub development history, and NVIDIA Inception membership information.

October 22: Microsoft informed me that my LinkedIn account was too recently created.

October 27: Support suggested that completing LinkedIn verification could allow the internal team to consider a final exception review.

October 28: I completed LinkedIn identity verification using South Korea's PASS identity system and Persona facial verification, then informed Microsoft.

November 5: Support again rejected my application, stating that my LinkedIn account was recently created and that my profile was not verified.

The case was then marked for closure without a clear explanation of why my completed verification was not recognized.

Here's what I find particularly concerning.

I created my LinkedIn account in June 2026 specifically because Microsoft required it for my startup application.

I had not previously needed LinkedIn to operate my business.

Microsoft asked me to create and verify a LinkedIn account. I followed those instructions and completed the requested identity verification.

Yet my application was still rejected partly because that same account was too new.

Why should the age of a social media account determine whether a legally registered startup is legitimate?

A LinkedIn account created five years ago does not automatically prove business legitimacy, just as an account created five months ago does not make a founder illegitimate.

I have provided government-issued identity verification, third-party facial verification, official corporate registration documents, and evidence of actual software development.

I also question whether my application received an independent manual review or whether the decisions were based primarily on automated screening results.

I understand that Microsoft needs fraud prevention measures, and I'm not asking for verification requirements to be bypassed.

However, I believe legitimate startup founders should have a transparent and reasonable way to verify their identity and business without being dependent on how long they have used LinkedIn.

My questions for Microsoft and other founders are:

Is there an official minimum LinkedIn account age for Microsoft for Startups eligibility?

If so, where is that requirement documented? Would waiting another few months make the same business eligible?

Why is a completed identity verification still being classified as unverified?

Is there an alternative verification process for founders who did not previously use LinkedIn?

Can applicants request an independent manual review when automated verification or internal system issues appear to be involved?

I've spent more than four months trying to resolve this issue through official support channels.

My goal is not just to obtain Azure credits. I would like to understand whether the verification process is functioning as intended and how other legitimate founders are expected to navigate it.

Has anyone else experienced similar problems with Microsoft for Startups verification, particularly with newly created LinkedIn accounts?

I'd also appreciate guidance from any Microsoft representative who can help direct this issue to the appropriate verification team.Title: Microsoft for Startups rejected my verified business because my LinkedIn account was too new — after four months of verification issues

I'm a South Korean startup founder operating ModuVoice (https://moduvoice.com), an AI-based speech technology service.

I've been trying to resolve a Microsoft for Startups verification issue since June 2026, and I'm sharing my experience because I believe it raises important questions about the program's verification process.

Here's what happened:

June: My business verification failed. Microsoft Support subsequently acknowledged an internal system issue preventing Business Verification reviews and manual intervention.

September: My initial $1,000 Azure startup credits had expired, and I opened another support case to resolve the verification issue.

October: I submitted my official South Korean business registration certificate, GitHub development history, and NVIDIA Inception membership information.

October 22: Microsoft informed me that my LinkedIn account was too recently created.

October 27: Support suggested that completing LinkedIn verification could allow the internal team to consider a final exception review.

October 28: I completed LinkedIn identity verification using South Korea's PASS identity system and Persona facial verification, then informed Microsoft.

November 5: Support again rejected my application, stating that my LinkedIn account was recently created and that my profile was not verified.

The case was then marked for closure without a clear explanation of why my completed verification was not recognized.

Here's what I find particularly concerning.

I created my LinkedIn account in June 2026 specifically because Microsoft required it for my startup application.

I had not previously needed LinkedIn to operate my business.

Microsoft asked me to create and verify a LinkedIn account. I followed those instructions and completed the requested identity verification.

Yet my application was still rejected partly because that same account was too new.

Why should the age of a social media account determine whether a legally registered startup is legitimate?

A LinkedIn account created five years ago does not automatically prove business legitimacy, just as an account created five months ago does not make a founder illegitimate.

I have provided government-issued identity verification, third-party facial verification, official corporate registration documents, and evidence of actual software development.

I also question whether my application received an independent manual review or whether the decisions were based primarily on automated screening results.

I understand that Microsoft needs fraud prevention measures, and I'm not asking for verification requirements to be bypassed.

However, I believe legitimate startup founders should have a transparent and reasonable way to verify their identity and business without being dependent on how long they have used LinkedIn.

My questions for Microsoft and other founders are:

Is there an official minimum LinkedIn account age for Microsoft for Startups eligibility?

If so, where is that requirement documented? Would waiting another few months make the same business eligible?

Why is a completed identity verification still being classified as unverified?

Is there an alternative verification process for founders who did not previously use LinkedIn?

Can applicants request an independent manual review when automated verification or internal system issues appear to be involved?

I've spent more than four months trying to resolve this issue through official support channels.

My goal is not just to obtain Azure credits. I would like to understand whether the verification process is functioning as intended and how other legitimate founders are expected to navigate it.

Has anyone else experienced similar problems with Microsoft for Startups verification, particularly with newly created LinkedIn accounts?

I'd also appreciate guidance from any Microsoft representative who can help direct this issue to the appropriate verification team.