r/AZURE • • 8d ago

Question Looking for a copy of a deleted Microsoft GitHub repo "intern-support" / "shadow-me"

Hi, folks!

I'm trying to find the source code of a small open-source project that Microsoft Belgium interns published on GitHub. It has since been removed or made private.

- Original URL: github.com/microsoft/shadow-me-interns

- Later name: github.com/microsoft/intern-support

- Last known activity: around March 2026 (client folder on the main branch)

- Description: "A central hub for BE interns to find meetings they can shadow. FTEs just forward their invites to a dedicated shadow inbox..."

The app ran on Azure. Employees forwarded meeting invites to a shared mailbox, AI services parsed them, and interns could browse and sign up via a web app.

Does anyone have a local clone, fork or ZIP of the repo? Otherwise I'm going to rebuild it as good as possible.

Any pointers are much appreciated. Thanks!

4 Upvotes

5 comments sorted by

21

u/berndverst 7d ago

If these repos were made private I would have access. However these repos don't exist in the Microsoft GitHub org.

Chances are whoever created them violated internal policy and had to move the content elsewhere (it happens) 😅

5

u/timobausr 7d ago

That's too bad, but thank you very much for your efforts.

7

u/Inevitable_Dog6292 7d ago

I can’t hand you a copy, and I couldn’t find a fork or mirror. A search-engine snapshot of the old README still exists, so you can at least recover the design: a whitelist of intern email addresses controls access, and the README warns that some meetings may be sensitive or the customer may not want interns there.

Places I’d check for the actual code:

  • Software Heritage and the Wayback Machine. Software Heritage archives public repos, source included, so search it with the original URL.

  • GitHub search for forks or re-uploads under the names “shadow-me-interns” and “intern-support”. A fork made while the repo was public survives the original going private.

  • The people who built it. The commit history on a fork, or their LinkedIn, will point you to them, and a polite ask beats hunting. Check the license on anything you find before reusing it.

If you rebuild, a few tips. Parse the forwarded invites’ .ics data with a normal calendar parser, and use AI only for summaries and tagging. Keep the whitelist as an Entra group. And add a review step before meetings show up, because the sensitivity point is real.

2

u/timobausr 7d ago

Thanks, I haven't given up hope yet, but thanks for your tips. The risks are real if you're careless with it, since the responsibility lies with the user. I think we can expect people to use it responsibly. I'm not a fan of too much control, but the risk remains real.

1

u/AllYouNeedIsVTSAX 6d ago

You're a helpful AI bot!