iamnoone

I am Invisible. I am no one.

Azure | Dynamics 365 | Technology
| Travel Enthusiast | I love my Honda

[iamnoone @imnoone_79]

Go to https://t.co/cW62pFzh1i or from the X main dashboard, click the three dots in the left sidebar, then select Creator Studio > Analytics.

[iamnoone @imnoone_79]

After the 1983 World Cup, Indian cricket entered a new era of dominance.
Sachin at the peak, followed by Kohli, Dhoni, Dravid, Kumble and the modern greats — this is the pyramid of impact and greatness.
Who’s your top pick from this generation?
#IndianCricket #After1983 #SachinTendulkar #ViratKohli #MSDhoni #TeamIndia #CricketGreats #WorldCupLegacy #PyramidOfGreatness

[iamnoone @imnoone_79]

Before the 1983 World Cup, these legends built the foundation of Indian cricket.
From Sunil Gavaskar’s batting masterclass to the spin quartet and early all-rounders — this is the pyramid of talent that paved the way for glory.
Who would you move up or down?
#IndianCricket #Before1983 #Gavaskar #KapilDev #SpinQuartet #CricketLegends #TeamIndia #CricketHistory

[iamnoone @imnoone_79]

Honda was often ahead of the curve in India with thoughtful, premium-feeling products.

City (1998): Premium sedan with refinement + later VTEC. Status symbol.

Jazz: Magic Seats (60:40 flexible folding). Practical premium hatch.

BR-V: Connected taillights. Distinctive design.

Civic: Paddle shifters (India first), futuristic dual-tier cluster, India’s first hybrid (2008), later LaneWatch.

CR-V: Early premium urban SUV; later diesel + 7-seater, panoramic sunroof, LaneWatch & more segment firsts.

Honda led with reliability & thoughtful tech. Then lost momentum — thin portfolio, late to SUVs and EV.

India deserves better reliable cars. Hope Honda’s new models & focus bring the brand back.

#Honda #HondaIndia #HondaCity #HondaCivic #HondaCRV #HondaJazz #BRV #ReliableCars #IndianAuto #CarMarketIndia #HondaComeback #MakeInIndia #AutoIndia #Sedan #SUV #Hybrid #HondaSensing #VTEC #MagicSeats #IndianCars #CarEnthusiasts #HondaLove #TrustHonda #BetterCarsIndia

[iamnoone @imnoone_79]

When buying a new car, don’t just go by review videos. Most reviewers are tall, so when they say rear seat width or legroom is “not enough,” it may still be fine for your family.

Take your family for the test drive and also sit in the rear yourself before deciding. When I checked, the Kylaq felt a bit narrow with limited space, while the Kushaq had better rear space and the Elevate offered good legroom too.

Comfort is personal — don’t decide only based on reviewers and influencers.

#CarBuyingTips #SUV #TestDrive #SkodaKylaq #HondaElevate #FamilyCar

[iamnoone @imnoone_79]

Car experts & influencers criticised the Honda Elevate facelift for only offering a 1.5L NA petrol (no turbo/hybrid).
The same voices are praising the Hyundai Bayon despite a similar 1.5L NA petrol + MT/IVT.

Novelty bias
New models with fresh tech get softer scrutiny. Updates to existing cars are judged harder on what didn’t change.

Selective framing
When a car fits the preferred narrative (screens, AI, design), powertrain limits are downplayed. When it doesn’t, the same limits are amplified.

Engagement incentives
“AI assistant” and dual screens drive more views than consistent criticism of a familiar NA engine.

Brand expectations
Honda is expected to lead on engines. Hyundai is expected to lead on features — so the standards shift.

Clear double standard in car reviews.
#HondaElevate #HyundaiBayon #CarReviews #DoubleStandards #AutoInfluencers #IndianAuto #CarExperts #AutomotiveMedia

[iamnoone @imnoone_79]

@AUTOINTELIN No nonsense car, no unnecessary tech gimmicks.

#HondaElevate #HondaCarIndia #NVH

[iamnoone @imnoone_79]

Everything’s going touchscreen these days like TVs, fridges, even elevators. Bigger screens, fewer buttons. That’s the trend.
But a lot of us still prefer simple physical controls that just work. That’s why the Elevate feels different. No nonsense car. Does what it needs to without the usual tech gimmicks.
@HondaCarIndia existing owners have been asking for a proper NVH kit for a while. Better seals and some damping for the older ones would actually help. Hope you consider it.
#HondaElevate #HondaCarIndia #NVH

[iamnoone @imnoone_79]

Everything’s going touchscreen these days like TVs, fridges, even elevators. Bigger screens, fewer buttons. That’s the trend.
But a lot of us still prefer simple physical controls that just work. That’s why the Elevate feels different. No nonsense car. Does what it needs to without the usual tech gimmicks.
@HondaCarIndia existing owners have been asking for a proper NVH kit for a while. Better seals and some damping for the older ones would actually help. Hope you consider it.
#HondaElevate #HondaCarIndia #NVH

[iamnoone @imnoone_79]

Elevate is not losing because it has no turbo or strong hybrid. Rivals sell on the same kind of engine it already has.
Creta’s 1.5 turbo petrol was only about 2% of 2025 sales. Diesel was about 44%, and most of the rest was the 1.5 NA petrol. Seltos is the same story: NA petrol and diesel do the volume, turbo does not. Grand Vitara’s strong hybrid was about 12% in August. Victoris strong hybrid was 272 units. The cars people actually buy in this segment are NA petrol, diesel, or factory CNG.
So a missing turbo or City-style hybrid does not explain a 1,730-unit September for the Elevate against 17,657 for the Creta. The engine type is not the gap. Something else is: brand pull, resale, variant pricing, automatic demand, dealer reach, or simply how the product is perceived next to Creta, Seltos and Victoris.
The facelift at least fixes the cabin complaint. Ventilated seats, a 360-degree camera, Type-C charging and the other feature adds put it closer to what buyers already tick on the rivals. The mechanicals are unchanged, still the 1.5 i-VTEC with a manual or CVT, which is fine if NA is what the segment buys.
If sales move now, it will be because the car finally feels updated, not because Honda added a turbo. Worth watching the next two or three months before calling the facelift a fix.

#HondaElevate #NewElevate #ElevateFacelift #Honda #HondaIndia #MidsizeSUV #CarSales #IndianAuto #NAPetrol #Creta #Seltos #Victoris #GrandVitara

[iamnoone @imnoone_79]

Five Azure Functions questions that go past the definition. Each one is a post on its own.

1. A function works locally and returns 403 in Azure. Where do you look first?

Not the token. A 401 is authentication. A 403 is the call arriving and the IP being rejected. Check Access restrictions on the function, then the target firewall. Consumption outbound IPs change. A rule for yesterday’s IP fails today. The stable fix is VNet integration and a subnet rule, not an IP list.

2. Why is the function log empty when the call fails?

The host never finished starting, or the platform blocked the call before the host. Typical causes are a missing app setting, `AzureWebJobsStorage` locked by a firewall, or Access restrictions. An empty log means the code did not run.

3. When do you use a Durable Function instead of a normal function?

When the work is longer than the plan timeout, needs a retry, or must wait for a human or another system. A normal function is one short run. A Durable Function is a workflow with state. Do not use it for a single HTTP call.

4. What is the difference between Consumption, Flex Consumption, and Premium?

Consumption scales to zero and cold-starts. No virtual network. Flex Consumption can keep an instance warm and supports a virtual network. Premium stays warm, supports a virtual network, and you pay for the reserved instances even when idle. A Dynamics call that must answer quickly does not belong on classic Consumption.

5. Why should a `ServiceClient` for Dataverse not be created inside `Run`?

Each call pays the connection cost, and a cold start gets slower. Register it once in `Program.cs` as a singleton. Keep the URL and secret in app settings. `local.settings.json` is never read in Azure.

#AzureFunctions #Azure #InterviewQuestions #Dynamics365 #Serverless

[iamnoone @imnoone_79]

The first call did not fail because the code was wrong. It failed because the plan had let the app go to sleep.

Azure Functions does not have one hosting model. The plan decides if the app can sleep, how bad the first call is, and what you pay for.

Consumption scales to zero. You pay only when it runs. The first call after idle is a cold start, the timeout tops out at 10 minutes, and there is no virtual network. Fine for a short uneven job. A bad fit if the caller cannot wait.

Flex Consumption still scales to zero, but you can keep an instance always ready. That removes the normal cold start. It supports a virtual network and longer runs. You pay per execution, plus a small charge for the warm instance.

Premium (EP1–EP3) stays warm. Pre-warmed instances mean a scale-out does not start cold. Virtual network, longer runs, more CPU. You pay for those instances even when traffic is low. Use this when a Dynamics or SQL call must answer quickly.

Dedicated means the function sits on an App Service plan next to a web app. It does not scale to zero. Cost is fixed.

Basic is for development. No slots, no autoscale.
Standard is the usual small production plan. Slots and autoscale.
Premium v3 is for a function sharing a plan with a busy web app.
Isolated v2 is only when compliance needs your own network boundary.

A prototype goes on Consumption. A Dynamics call that must answer an HTTP request goes on Flex Consumption with one always-ready instance, or on Premium. Do not put that call on classic Consumption and then try to code past the cold start.

#AzureFunctions #Azure #AppService #Serverless #Cloud

[iamnoone @imnoone_79]

A 403 from a Function App usually means the call arrived and the IP was rejected. A bad token is 401. An IP block is 403, and your code never runs.

The function does not call out from your laptop. Consumption uses a shared outbound IP that can change between runs. Premium, Flex, and Dedicated use the plan’s outbound addresses, and a scale-out adds more. A firewall rule for the one IP you copied yesterday fails the next morning.

The IP list on the Function App properties page is not a contract. Use it only to prove the cause. The stable fix is VNet integration with Route All, then allow the subnet on the target. A service endpoint is enough for Storage or SQL. A private endpoint is the better fit for Key Vault, Storage, and a Dynamics or Dataverse lock-down. The private DNS zone must be linked to that VNet, or the name still resolves to the public IP and the firewall blocks it again.

If the 403 is on the function URL, open Access restrictions. A rule for the office IP blocks every other caller, including Logic Apps and Dynamics webhooks. The platform returns 403 before the host starts, so the invocation log is empty. That empty log is the clue.

Check in this order. Access restrictions on the function. The target firewall or conditional access. The outbound IP the plan is using now. Then the code.

A Dynamics call has one more trap. The app registration can be valid and the IP still fails if the environment allows only selected addresses. Allow the subnet, not a single function IP.

#AzureFunctions #Azure #Networking #403Forbidden #VNet #PrivateEndpoint #Dynamics365

[iamnoone @imnoone_79]

@HondaCarIndia : Existing Elevate owners will pay for two fixes.

A genuine NVH kit (better door seals + damping) fitted at Honda workshops. Highway cabin noise is the one complaint that keeps coming back.

Add a rear USB-C and remove the 12V socket

Paid accessory > ignored feedback.

Loyalty is cheaper to keep than to rebuild.
#HondaElevate #HondaIndia #newHondaElevate

[iamnoone @imnoone_79]

@HondaCarIndia : Existing Elevate owners will pay for two fixes.

A genuine NVH kit (better door seals + damping) fitted at Honda workshops. Highway cabin noise is the one complaint that keeps coming back.

Add a rear USB-C and remove the 12V socket

Paid accessory > ignored feedback.

Loyalty is cheaper to keep than to rebuild.
#HondaElevate #HondaIndia #newHondaElevate

[iamnoone @imnoone_79]

A 403 from a Function App usually means the call arrived and the IP was rejected. A bad token is 401. An IP block is 403, and your code never runs.

The function does not call out from your laptop. Consumption uses a shared outbound IP that can change between runs. Premium, Flex, and Dedicated use the plan’s outbound addresses, and a scale-out adds more. A firewall rule for the one IP you copied yesterday fails the next morning.

The IP list on the Function App properties page is not a contract. Use it only to prove the cause. The stable fix is VNet integration with Route All, then allow the subnet on the target. A service endpoint is enough for Storage or SQL. A private endpoint is the better fit for Key Vault, Storage, and a Dynamics or Dataverse lock-down. The private DNS zone must be linked to that VNet, or the name still resolves to the public IP and the firewall blocks it again.

If the 403 is on the function URL, open Access restrictions. A rule for the office IP blocks every other caller, including Logic Apps and Dynamics webhooks. The platform returns 403 before the host starts, so the invocation log is empty. That empty log is the clue.

Check in this order. Access restrictions on the function. The target firewall or conditional access. The outbound IP the plan is using now. Then the code.

A Dynamics call has one more trap. The app registration can be valid and the IP still fails if the environment allows only selected addresses. Allow the subnet, not a single function IP.

#AzureFunctions #Azure #Networking #403Forbidden #VNet #PrivateEndpoint #Dynamics365

[iamnoone @imnoone_79]

The first call did not fail because the code was wrong. It failed because the plan had let the app go to sleep.

Azure Functions does not have one hosting model. The plan decides if the app can sleep, how bad the first call is, and what you pay for.

Consumption scales to zero. You pay only when it runs. The first call after idle is a cold start, the timeout tops out at 10 minutes, and there is no virtual network. Fine for a short uneven job. A bad fit if the caller cannot wait.

Flex Consumption still scales to zero, but you can keep an instance always ready. That removes the normal cold start. It supports a virtual network and longer runs. You pay per execution, plus a small charge for the warm instance.

Premium (EP1–EP3) stays warm. Pre-warmed instances mean a scale-out does not start cold. Virtual network, longer runs, more CPU. You pay for those instances even when traffic is low. Use this when a Dynamics or SQL call must answer quickly.

Dedicated means the function sits on an App Service plan next to a web app. It does not scale to zero. Cost is fixed.

Basic is for development. No slots, no autoscale.
Standard is the usual small production plan. Slots and autoscale.
Premium v3 is for a function sharing a plan with a busy web app.
Isolated v2 is only when compliance needs your own network boundary.

A prototype goes on Consumption. A Dynamics call that must answer an HTTP request goes on Flex Consumption with one always-ready instance, or on Premium. Do not put that call on classic Consumption and then try to code past the cold start.

#AzureFunctions #Azure #AppService #Serverless #Cloud

[iamnoone @imnoone_79]

The SIR process has been smooth for us and our relatives.

My wife and I were on the 2002 voter list, before our marriage. We linked that old entry in the enumeration form. Both our names are now in the draft voter list.

My father died in 2015. We had asked several times to remove his name, but it was never done. Under SIR, his name is on the Unreachable list. I hope it is deleted from the next voter list, so it cannot be used for bogus voting.

I also filled Form 6 to add my daughter. In the declaration, there is an option for the 2025/2026 SIR. When I selected it and searched, my name did not appear. I think this is because the 2025/2026 SIR is not yet complete in Maharashtra. The website does not explain this clearly. I submitted Form 6 a week ago, and there has been no update so far.

#SIR #VoterList #ElectoralRoll #ECI #Maharashtra #Form6 #DraftVoterList #Vote

[iamnoone @imnoone_79]

Neha Bora, national president of AISA, is the dynamic, vocal ultra-Left face of Gen Z, with a real following on the Left. As the Left shrinks across India, she is expected to join Congress and contest West Delhi in 2029 — the same route Kanhaiya Kumar took from the CPI to Congress.
#NehaBora #KanhaiyaKumar #WestDelhi #LokSabha2029 #Congress #GenZ #AISA #DelhiElections

[iamnoone @imnoone_79]

Happy with India’s batting right now. The numbers look elite.
But the 2027 World Cup is in South Africa, Zimbabwe and Namibia. Those are not Indian flat wickets.
Highveld bounce, extra carry, steeper length. The same shots that look easy at home can become edges there.
India should prepare on a few true, bouncy pitches at home. Keep the batting confidence. Just don’t let the World Cup be the first time the ball gets up.
#TeamIndia #CricketWorldCup2027 #INDvsWI #CWC27 #IndianCricket