microsoft / microsoft/finops-toolkit

Recommended upskilling readiness for FinOps Hub

Open
#2,044 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Skill: Documentation Tool: FinOps hubs Type: Feature 💎
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

📝 Scenario

As a FinOps Practitioner/Engineer, I need to ready myself via upskilling in order to deploy and maintain the FinOps? Why is this needed? I know more about Azure than I do about Fabric and data analytics

💎 Solution

TODO: Generate a list of FinOps Hub components (Azure, Fabric, FinOps, FOCUS, etc..) and the expected knowledge, skills, or experience that would be beneficial (not required) for implementation, management, maintenance, or usage of the FinOps Hub.

📋 Tasks

Add a recommended topic/knowledge list for Azure
Add a recommended topic/knowledge list for Fabric
Add a recommended topic/knowledge list for FinOps

### Stretch goals
- [ ] TODO: Add tasks

ℹ️ Additional context

Not expecting specific or detailed upskilling to be listed or defined. We can search LinkedIn Learning, Udemy, Coursera, or the FinOps Foundation, or use AI assistance for relevant information.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by reviewing the FinOps Hub components listed in the issue and the suggested FinOps Foundation, LinkedIn Learning, Udemy, and Coursera sources. Done means adding organized recommended knowledge lists for Azure, Fabric, and FinOps, including relevant implementation, management, maintenance, or usage topics.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.